Triple
T27273827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yax Kʼukʼ Moʼ |
E688129
|
entity |
| Predicate | hasMayaNameMeaning |
P24069
|
FINISHED |
| Object | First Quetzal Macaw |
—
|
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: First Quetzal Macaw | Statement: [Yax Kʼukʼ Moʼ, hasMayaNameMeaning, First Quetzal Macaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMayaNameMeaning Context triple: [Yax Kʼukʼ Moʼ, hasMayaNameMeaning, First Quetzal Macaw]
-
A.
hasMayaName
Indicates that an entity is associated with or identified by a specific name in the Maya language or naming system.
-
B.
hasNameInYucatecMaya
Indicates that an entity is known by a particular name when expressed in the Yucatec Maya language.
-
C.
hasNameMeaningRelation
Indicates that there is a relationship between an entity and a name that conveys or encodes a particular meaning or significance.
-
D.
possibleNameMeaning
Indicates that a given interpretation or semantic meaning is a plausible or potential meaning of a specified name.
-
E.
hasGivenNameMeaning
chosen
Indicates that a given name carries a particular meaning or semantic interpretation.
- 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_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: April 27, 2026, 11:01 a.m.