Triple
T6561489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yucatecan branch |
E153792
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object |
Mopan language
The Mopan language is a Mayan language spoken primarily by the Mopan Maya people in Belize and Guatemala.
|
E600290
|
NE FINISHED |
How this triple was built (4 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: Mopan language | Statement: [Yucatecan branch, hasMember, Mopan language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mopan language Context triple: [Yucatecan branch, hasMember, Mopan language]
-
A.
Piapoco language
The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
-
B.
Yucuna language
The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
-
C.
Guarijío language
The Guarijío language is an indigenous Uto-Aztecan language spoken by the Guarijío people of northern Mexico, particularly in the states of Chihuahua and Sonora.
-
D.
Maricopa language
Maricopa language is a Native American Yuman language traditionally spoken by the Maricopa people of the lower Colorado River region in the southwestern United States.
-
E.
Sipakapense language
The Sipakapense language is a Mayan language spoken by the Sipakapense people in the western highlands of Guatemala.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Mopan language Triple: [Yucatecan branch, hasMember, Mopan language]
Generated description
The Mopan language is a Mayan language spoken primarily by the Mopan Maya people in Belize and Guatemala.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Mopan language Target entity description: The Mopan language is a Mayan language spoken primarily by the Mopan Maya people in Belize and Guatemala.
-
A.
Piapoco language
The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
-
B.
Yucuna language
The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
-
C.
Guarijío language
The Guarijío language is an indigenous Uto-Aztecan language spoken by the Guarijío people of northern Mexico, particularly in the states of Chihuahua and Sonora.
-
D.
Maricopa language
Maricopa language is a Native American Yuman language traditionally spoken by the Maricopa people of the lower Colorado River region in the southwestern United States.
-
E.
Sipakapense language
The Sipakapense language is a Mayan language spoken by the Sipakapense people in the western highlands of Guatemala.
- F. None of above. chosen
Provenance (5 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ae37a5b0819091692fc5def270b9 |
completed | March 27, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6cb90ffd48190996a64d79f516e2c |
completed | March 27, 2026, 6:25 p.m. |
| NEDg | Description generation | batch_69c6cd05c54c81908bb612e7976bd10a |
completed | March 27, 2026, 6:31 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c6cdc3ea7c8190b63e9a19721fea80 |
completed | March 27, 2026, 6:34 p.m. |
Created at: March 27, 2026, 1:52 p.m.