Triple
T11316112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chimuan languages |
E267970
|
entity |
| Predicate | notableLanguage |
P207
|
FINISHED |
| Object | Mochica language |
E128096
|
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: Mochica language | Statement: [Chimuan languages, notableLanguage, Mochica language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mochica language Context triple: [Chimuan languages, notableLanguage, Mochica language]
-
A.
Mochica language
chosen
The Mochica language is an extinct pre-Columbian language once spoken on the northern coast of Peru, associated with the Moche (Mochica) civilization.
-
B.
Sipakapense language
The Sipakapense language is a Mayan language spoken by the Sipakapense people in the western highlands of Guatemala.
-
C.
Secoya language
The Secoya language is a Western Tucanoan language spoken by the Secoya people of the Amazonian regions of Ecuador and Peru.
-
D.
Yaneshaʼ language
Yaneshaʼ language is an Arawakan indigenous language spoken by the Yaneshaʼ people in the central Peruvian Amazon.
-
E.
Piapoco language
The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c3cf748190987838029d9f7fff |
completed | April 9, 2026, 6:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e50a9e66588190b71e0f60133a8995 |
completed | April 19, 2026, 5:02 p.m. |
Created at: April 8, 2026, 9:32 p.m.