Triple
T22168021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canaima village |
E547845
|
entity |
| Predicate | governingCountryOfficialLanguage |
P95654
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [Canaima village, governingCountryOfficialLanguage, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingCountryOfficialLanguage Context triple: [Canaima village, governingCountryOfficialLanguage, Spanish]
-
A.
governingCountryLanguage
Indicates that a particular language is officially used or recognized by the governing authorities of a given country.
-
B.
hasLanguageOfficial
Indicates that a language holds official status within a given entity, such as a country, region, or organization.
-
C.
hasOfficialCountryLanguage
chosen
Indicates that a country recognizes a particular language as one of its official languages for governmental or legal purposes.
-
D.
countryOfficialLanguageStatus
Indicates the status or role that a particular language holds as an official language within a given country.
-
E.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6642b08190980fa0c0d2bb4229 |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.