Triple
T11596104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baganda |
E275004
|
entity |
| Predicate | populationStatusInUganda |
P30459
|
FINISHED |
| Object | largest ethnic group in Uganda |
—
|
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 in Uganda | Statement: [Baganda, populationStatusInUganda, largest ethnic group in Uganda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationStatusInUganda Context triple: [Baganda, populationStatusInUganda, largest ethnic group in Uganda]
-
A.
regionInUganda
Indicates that a region or area is geographically located within the country of Uganda.
-
B.
primaryStatusInUganda
Indicates the primary legal, social, or operational status an entity holds specifically within the context of Uganda.
-
C.
distanceFromKampala
Indicates the measured distance between a given location and the city of Kampala.
-
D.
populationScale
chosen
Indicates the relative size or magnitude of a population, typically categorizing it into broad scale levels (e.g., small, medium, large).
-
E.
dividedPopulationOf
Indicates that a population has been split into distinct subgroups or segments, typically based on specified criteria or characteristics.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8946790d08190924d60bb4b523250 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.