Triple
T16616719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocom Maya |
E403713
|
entity |
| Predicate | hasDynastyName |
P23456
|
FINISHED |
| Object | Cocom |
E403713
|
NE 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: Cocom | Statement: [Cocom Maya, hasDynastyName, Cocom]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cocom Context triple: [Cocom Maya, hasDynastyName, Cocom]
-
A.
Cocom Maya
chosen
The Cocom Maya were a powerful Maya dynasty and polity in the Yucatán Peninsula, known for ruling from the city of Mayapán and resisting Spanish conquest in the 16th century.
-
B.
Nicoo
Nicoo is an alternative spelling or variant form of the name Nico, often used as a personal or online nickname.
-
C.
Kom Kom
Kom Kom is a musical work associated with the artist Mama Africa, likely reflecting her signature Afrocentric style and themes.
-
D.
Mocomoco
Mocomoco is a small town in Bolivia’s La Paz Department, situated within the rural Camacho Province in the Andean highlands.
-
E.
COCO
COCO is a large-scale, richly annotated image dataset widely used in computer vision research for tasks like object detection, segmentation, and captioning.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754ac9dc8190965197024594742b |
completed | April 18, 2026, 12:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a007daef18481908c3628a3466300ce |
completed | May 10, 2026, 12:44 p.m. |
Created at: April 10, 2026, 5:17 a.m.