Triple
T11469356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buga language |
E271860
|
entity |
| Predicate | useInOfficialContexts |
P24110
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Buga language, useInOfficialContexts, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useInOfficialContexts Context triple: [Buga language, useInOfficialContexts, none]
-
A.
usedInFormalContexts
Indicates that something is employed or occurs primarily within formal or official situations, settings, or styles of communication.
-
B.
notOfficialIn
Indicates that an entity does not hold an official role, status, or position within a specified organization, group, or jurisdiction.
-
C.
usedInOfficialDocumentsOf
Indicates that something (e.g., a term, symbol, or format) is employed within the formal or legally recognized documents issued by a particular entity or jurisdiction.
-
D.
hasOfficialUse
chosen
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
-
E.
usedInMachineReadableContexts
Indicates that something is employed or applied within formats or environments that can be automatically processed and interpreted by machines.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d82949e3688190b024a4980666c94f |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.