Triple
T37100877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Dagaare |
E918697
|
entity |
| Predicate | hasEthnologueEntryUnder |
P19233
|
FINISHED |
| Object | Dagaare |
—
|
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: Dagaare | Statement: [Northern Dagaare, hasEthnologueEntryUnder, Dagaare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnologueEntryUnder Context triple: [Northern Dagaare, hasEthnologueEntryUnder, Dagaare]
-
A.
hasEthnologueEntry
chosen
Indicates that there exists an entry for the subject in the Ethnologue language reference resource.
-
B.
hasEthnologueName
Indicates that an entity is associated with a specific language name as recorded in the Ethnologue reference.
-
C.
ethnologueScope
Indicates the classification scope or coverage category assigned to a language or variety within the Ethnologue system.
-
D.
hasGlottologEntry
Indicates that there exists a corresponding entry for the entity in the Glottolog linguistic database.
-
E.
hasEthnolinguisticPresence
Indicates that a particular ethnolinguistic group is present or represented within a specified place, context, or population.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:14 p.m.