Triple
T2193700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omaha people |
E49920
|
entity |
| Predicate | demographicCenter |
P25074
|
FINISHED |
| Object | Omaha Reservation communities |
—
|
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: Omaha Reservation communities | Statement: [Omaha people, demographicCenter, Omaha Reservation communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demographicCenter Context triple: [Omaha people, demographicCenter, Omaha Reservation communities]
-
A.
hasDemographicCenter
chosen
Indicates that an entity has a primary geographic location where the majority or core concentration of its associated population or demographic group is found.
-
B.
geographicCenter
Indicates the location that serves as the central point of a geographic area or region.
-
C.
hasPopulationCenter
Indicates that an area, region, or administrative unit contains or is served by a primary settlement or population hub.
-
D.
hasPopulationCenterType
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
-
E.
hasPopulationCenterDensity
Indicates the density of population centers within a given area or region.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf4a542881908aaaf4f0f85bc32c |
completed | March 7, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.