Triple
T27273828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yax Kʼukʼ Moʼ |
E688129
|
entity |
| Predicate | hasMayaNameElement |
P73760
|
FINISHED |
| Object | yax (first, new, green) |
—
|
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: yax (first, new, green) | Statement: [Yax Kʼukʼ Moʼ, hasMayaNameElement, yax (first, new, green)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMayaNameElement Context triple: [Yax Kʼukʼ Moʼ, hasMayaNameElement, yax (first, new, green)]
-
A.
hasMayaName
chosen
Indicates that an entity is associated with or identified by a specific name in the Maya language or naming system.
-
B.
hasElementName
Indicates that an entity is associated with, or identified by, a specific element name.
-
C.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
-
D.
hasProperNameElement
Indicates that an entity’s proper name includes a specific component (such as a word, phrase, or segment) as one of its constituent elements.
-
E.
hasFamilyNameElement
Indicates that an entity has a specific component or segment that forms part of its family name.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 27, 2026, 11:01 a.m.