Triple
T9259219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mooré |
E222528
|
entity |
| Predicate | statusInBurkinaFaso |
P87839
|
FINISHED |
| Object | major national 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: major national language | Statement: [Mooré, statusInBurkinaFaso, major national language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInBurkinaFaso Context triple: [Mooré, statusInBurkinaFaso, major national language]
-
A.
statusInGhana
Indicates the legal, social, or official standing or condition an entity holds within the context of Ghana.
-
B.
statusInMali
Indicates the legal, social, or official condition or standing that an entity holds within the context of Mali.
-
C.
statusInFrance
Indicates the legal, social, or official standing or condition that an entity has within the jurisdiction of France.
-
D.
statusInSuriname
Indicates the legal, social, or official standing or condition that an entity holds within the context of Suriname.
-
E.
statusInBolivia
Indicates the legal, social, or operational condition or standing that something or someone has within the context of Bolivia.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0714317481908405f857a4f49e74 |
completed | April 1, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:32 p.m.