Triple
T27242483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baniva |
E687244
|
entity |
| Predicate | countryStatusInColombia |
P192633
|
FINISHED |
| Object | Indigenous language |
—
|
LITERAL 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: Indigenous language | Statement: [Baniva, countryStatusInColombia, Indigenous language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryStatusInColombia Context triple: [Baniva, countryStatusInColombia, Indigenous language]
-
A.
positionInColombia
Indicates that one entity occupies or is located at a specific position within the geographic boundaries of Colombia.
-
B.
mainColombianDepartment
Indicates that one entity is the primary administrative department (region) associated with another entity within Colombia.
-
C.
countryStatus
Indicates the political or legal condition of a country, such as its sovereignty, recognition, or current state in international or domestic contexts.
-
D.
populationRankInValleDelCauca
Indicates the relative position of an entity in terms of population size compared to other entities within Valle del Cauca.
-
E.
nameInColombia
Indicates that an entity is known or referred to by a particular name specifically within the context of Colombia.
- F. None of above. chosen
Provenance (4 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: April 27, 2026, 10:38 a.m.