Triple
T15366257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Venezuela |
E367420
|
entity |
| Predicate | hasEthnicGroup |
P1898
|
FINISHED |
| Object | Yukpa |
E215479
|
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: Yukpa | Statement: [Western Venezuela, hasEthnicGroup, Yukpa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yukpa Context triple: [Western Venezuela, hasEthnicGroup, Yukpa]
-
A.
Yukpa language
chosen
The Yukpa language is an indigenous Cariban language spoken by the Yukpa people in the border regions of northeastern Colombia and western Venezuela.
-
B.
Sayultec
Sayultec is an indigenous Mixe–Zoquean language spoken by the Sayula Popoluca people of southern Veracruz, Mexico.
-
C.
Piapoco language
The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
-
D.
Yucuna language
The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
-
E.
Northern Pame
Northern Pame is a variety of the Pame language spoken by the Pame people of central Mexico, distinguished by its own phonological and grammatical features.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e497de48190be249b110999ec5c |
completed | April 16, 2026, 1:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff0b4e968c8190a16824ee3ede13b2 |
completed | May 9, 2026, 10:24 a.m. |
Created at: April 10, 2026, 3:18 a.m.