Triple
T22951768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pemón |
E570038
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Pemón language |
—
|
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: Pemón language | Statement: [Pemón, language, Pemón language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pemón language Context triple: [Pemón, language, Pemón language]
-
A.
Pemon language
chosen
Pemon language is an indigenous Cariban language spoken primarily by the Pemon people of southeastern Venezuela and neighboring regions of Brazil and Guyana.
-
B.
Piapoco language
The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
-
C.
Yucuna language
The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
-
D.
Tepehuán language
The Tepehuán language is a Uto-Aztecan indigenous language of northern Mexico spoken by the Tepehuán people in several regional dialects.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181a285448190a718734fe933d51a |
completed | April 29, 2026, 3:57 a.m. |
Created at: April 17, 2026, 3:46 p.m.