Triple
T2841926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ijesha |
E62488
|
entity |
| Predicate | sharesLanguageFamilyWith |
P33593
|
FINISHED |
| Object | other Yoruba dialects |
—
|
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: other Yoruba dialects | Statement: [Ijesha, sharesLanguageFamilyWith, other Yoruba dialects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesLanguageFamilyWith Context triple: [Ijesha, sharesLanguageFamilyWith, other Yoruba dialects]
-
A.
areOfficialLanguageFamilyOf
Indicates that one or more language families hold official status within, or are formally recognized as official for, a particular entity (such as a country or region).
-
B.
sharesLanguageWith
chosen
Indicates that two entities use at least one common language for communication.
-
C.
languageFamilyAssociated
Indicates that there is an association or connection between a language and a particular language family.
-
D.
derivedFromLanguageFamily
Indicates that one language originates from, or historically descends from, a particular language family.
-
E.
influencedLanguageFamily
Indicates that one language family has had a significant impact on the development, structure, or usage of another language family.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf16d0c08190bb8de4a4160b4414 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.