Triple
T37047692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tem language |
E916961
|
entity |
| Predicate | hasSpeakersInDiaspora |
P27697
|
FINISHED |
| Object | Nigeria |
—
|
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: Nigeria | Statement: [Tem language, hasSpeakersInDiaspora, Nigeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeakersInDiaspora Context triple: [Tem language, hasSpeakersInDiaspora, Nigeria]
-
A.
spokenInDiaspora
chosen
Indicates that a language or dialect is used by a community living outside its original homeland or region of origin.
-
B.
hasSpeakersAmong
Indicates that a group, event, or entity includes one or more speakers drawn from a specified set or category.
-
C.
hasSpeakersIn
Indicates that an entity (such as an event, conference, or session) includes or is associated with speakers located in or belonging to a specified place or group.
-
D.
hasSpeakersAlong
Indicates that something is equipped with or accompanied by speakers positioned along its length or path.
-
E.
haveSpeakersWhoAre
Indicates that an entity has speakers characterized by a specified property, status, or attribute.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
Created at: May 3, 2026, 4:14 p.m.