Triple
T28862468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiquitano language family |
E728898
|
entity |
| Predicate | mainContactLanguageCountry |
P46872
|
FINISHED |
| Object | Bolivia |
—
|
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: Bolivia | Statement: [Chiquitano language family, mainContactLanguageCountry, Bolivia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainContactLanguageCountry Context triple: [Chiquitano language family, mainContactLanguageCountry, Bolivia]
-
A.
primaryLanguageContact
chosen
Indicates that one language serves as the main or dominant medium of communication in a particular contact situation between language communities.
-
B.
primaryLanguageCountry
Indicates that a given language is the main or officially predominant language used within a particular country.
-
C.
countryOfLanguage
Indicates that a particular language is officially or predominantly used within a specified country.
-
D.
governingCountryLanguage
Indicates that a particular language is officially used or recognized by the governing authorities of a given country.
-
E.
hostCountryLanguageContext
Indicates the linguistic environment or language norms present in the country where an entity is hosted or operating.
- F. None of above.
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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 6:47 a.m.