Triple
T24731134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabelbala |
E618289
|
entity |
| Predicate | korandjeFamily |
P157210
|
FINISHED |
| Object | Songhay languages (highly divergent) |
—
|
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: Songhay languages (highly divergent) | Statement: [Tabelbala, korandjeFamily, Songhay languages (highly divergent)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: korandjeFamily Context triple: [Tabelbala, korandjeFamily, Songhay languages (highly divergent)]
-
A.
coreFamily
Indicates that one entity belongs to the other’s immediate (nuclear) family, such as parent, child, or sibling.
-
B.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
C.
enemyFamily
Indicates that two entities belong to families that are hostile or in conflict with each other.
-
D.
familia
Indicates a familial relationship or bond between entities, such as being members of the same family.
-
E.
creatorFamily
Indicates that one entity is a family member of the creator or originator of another entity.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f422add8508190a76e56cfa756eeb8 |
completed | May 1, 2026, 3:49 a.m. |
Created at: April 18, 2026, 4:02 a.m.