Triple
T26552616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya of Copán |
E671718
|
entity |
| Predicate | firstKnownRuler |
P128624
|
FINISHED |
| Object | Kʼinich Yax Kʼukʼ Moʼ |
—
|
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ʼinich Yax Kʼukʼ Moʼ | Statement: [Maya of Copán, firstKnownRuler, Kʼinich Yax Kʼukʼ Moʼ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstKnownRuler Context triple: [Maya of Copán, firstKnownRuler, Kʼinich Yax Kʼukʼ Moʼ]
-
A.
firstMonarch
Indicates that the subject is the first monarch (initial ruler) of the object polity or domain.
-
B.
earliestWellAttestedKing
Indicates that the subject is recognized as the earliest historically well-documented king of the referenced polity or lineage.
-
C.
firstMonarchOfCurrentDynastyReignStart
Indicates the date or time when the reign of the first monarch of the current ruling dynasty began.
-
D.
traditionalFirstEmperorReignStart
Indicates the traditionally recognized starting date of the first emperor’s reign over a given polity or realm.
-
E.
firstKnownLord
chosen
Indicates that the subject is the earliest historically or canonically recorded lord associated with the object.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: April 27, 2026, 1:48 a.m.