Triple
T18947090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Dalmatia |
E463541
|
entity |
| Predicate | partOfRoyalStyle |
P78578
|
FINISHED |
| Object | Hungarian royal titles |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Hungarian royal titles | Statement: [King of Dalmatia, partOfRoyalStyle, Hungarian royal titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfRoyalStyle Context triple: [King of Dalmatia, partOfRoyalStyle, Hungarian royal titles]
-
A.
royalStyle
Indicates the formal manner or title by which a monarch or royal person is officially addressed or referred to.
-
B.
royalUse
Indicates that something is used, employed, or reserved specifically by or for a royal person or royal institution.
-
C.
royalTitularyFeature
chosen
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
-
D.
royalStandard
Indicates that an entity is the official royal flag or emblem used to represent a monarch or royal authority.
-
E.
hasRoyalHousehold
Indicates that an entity possesses or is associated with a specific royal household as its official domestic or courtly establishment.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5402ad881908add559249278895 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.