Triple
T9606318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alur language |
E231979
|
entity |
| Predicate | subfamilyWithinWesternNilotic |
P10928
|
FINISHED |
| Object | Luo languages |
—
|
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: Luo languages | Statement: [Alur language, subfamilyWithinWesternNilotic, Luo languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subfamilyWithinWesternNilotic Context triple: [Alur language, subfamilyWithinWesternNilotic, Luo languages]
-
A.
subfamily
Indicates that one taxonomic group is a subfamily within a larger family, representing an intermediate rank in biological classification.
-
B.
belongsToSubfamily
chosen
Indicates that one entity is a member of, or classified within, a specific subfamily of another entity.
-
C.
subbranchOf
Indicates that one entity is a subordinate or secondary branch derived from, and structurally dependent on, another entity.
-
D.
sisterSubdivision
Indicates that two administrative or organizational subdivisions share a common parent division and are thus parallel or peer units to each other.
-
E.
subTribeOf
Indicates that one tribe is a subordinate or constituent part of a larger, parent tribe.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a6006d48190adc03306533b9be6 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.