Triple
T6220825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinka people |
E139107
|
entity |
| Predicate | populationRankInSouthSudan |
P25930
|
FINISHED |
| Object | largest ethnic group |
—
|
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: largest ethnic group | Statement: [Dinka people, populationRankInSouthSudan, largest ethnic group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationRankInSouthSudan Context triple: [Dinka people, populationRankInSouthSudan, largest ethnic group]
-
A.
populationRankInSudan
Indicates the relative position of an entity in terms of population size compared to other entities within Sudan.
-
B.
hasPopulationRank
Indicates the relative position of an entity in an ordered list based on the size of its population.
-
C.
populationRank
Indicates the relative position of an entity in an ordered list based on the size of its population.
-
D.
hasPopulationRankInRegion
chosen
Indicates that an entity has a specific population-based rank or position within a defined geographic region.
-
E.
populationRankAfter
Indicates the relative position of an entity in a population-based ordering that comes after another entity’s population rank.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062bcc2348190806ed8c98bdfbf3e |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.