Triple
T25215610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dosso Zarma |
E631819
|
entity |
| Predicate | spokenPrimarilyAround |
P67236
|
FINISHED |
| Object | Dosso area |
—
|
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: Dosso area | Statement: [Dosso Zarma, spokenPrimarilyAround, Dosso area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenPrimarilyAround Context triple: [Dosso Zarma, spokenPrimarilyAround, Dosso area]
-
A.
spokenPrimarilyOn
Indicates that something (typically a language or dialect) is used mainly for spoken communication in a particular context, region, or group.
-
B.
spokenInLocality
Indicates that a language, dialect, or speech form is used or spoken within a specific locality or geographic area.
-
C.
isSpokenAround
chosen
Indicates that something (such as a language, phrase, or expression) is commonly spoken in the vicinity of, or within the general area surrounding, a particular place or entity.
-
D.
spokenInCountryColloquialLanguage
Indicates that a language is informally or colloquially spoken within a particular country.
-
E.
isSpokenOn
Indicates that a particular language, phrase, or utterance is used or occurs during a specified time, event, or occasion.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47b8d14c48190a744ce7dd1680150 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:59 p.m.