Triple
T33257006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walthill, Nebraska |
E851400
|
entity |
| Predicate | governingTribalAuthorityNearby |
P43178
|
FINISHED |
| Object | Omaha Tribe of Nebraska |
—
|
NE NERFINISHED |
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 Tribe of Nebraska | Statement: [Walthill, Nebraska, governingTribalAuthorityNearby, Omaha Tribe of Nebraska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingTribalAuthorityNearby Context triple: [Walthill, Nebraska, governingTribalAuthorityNearby, Omaha Tribe of Nebraska]
-
A.
hasNearbyTribalAgency
Indicates that a tribal agency is located in close geographic proximity to the referenced entity.
-
B.
governingTribalPresence
chosen
Indicates that an entity holds governing authority or administrative control over a tribal presence in a given area or context.
-
C.
hasTribalHeadquartersNearby
Indicates that the subject entity is located close to the tribal headquarters of a Native nation or tribe.
-
D.
nearTribalGroup
Indicates that one entity is located geographically close to a tribal group.
-
E.
associatedTribalGovernment
Indicates a relationship where an entity is formally linked or connected to a specific tribal government.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a008d6085508190a71c52cd028a6297 |
completed | May 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a008ced31448190b8fc60bf87b40647 |
completed | May 10, 2026, 1:49 p.m. |
Created at: May 1, 2026, 1:31 a.m.