Triple
T25393149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kʼinich Kʼan Joy Chitam II |
E636220
|
entity |
| Predicate | hasRoyalTitleElement |
P78578
|
FINISHED |
| Object | Kʼan |
—
|
NE NERFINISHED |
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: Kʼan | Statement: [Kʼinich Kʼan Joy Chitam II, hasRoyalTitleElement, Kʼan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalTitleElement Context triple: [Kʼinich Kʼan Joy Chitam II, hasRoyalTitleElement, Kʼan]
-
A.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
B.
usesRoyalTitle
Indicates that one entity refers to another using a royal title or honorific (such as king, queen, prince, or similar).
-
C.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
D.
isHighestRoyalTitleIn
Indicates that a royal title is the most senior or supreme title within a specified realm, hierarchy, or political entity.
-
E.
royalTitularyFeature
chosen
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 21, 2026, 1:49 p.m.