Triple
T23830480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Pitch Utes |
E589498
|
entity |
| Predicate | modernSuccessorGroup |
P81788
|
FINISHED |
| Object | Ute Indian Tribe of the Uintah and Ouray Reservation |
—
|
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: Ute Indian Tribe of the Uintah and Ouray Reservation | Statement: [San Pitch Utes, modernSuccessorGroup, Ute Indian Tribe of the Uintah and Ouray Reservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSuccessorGroup Context triple: [San Pitch Utes, modernSuccessorGroup, Ute Indian Tribe of the Uintah and Ouray Reservation]
-
A.
successorGroups
chosen
Indicates that one group is the direct successor or follow-up group to another group in some sequence or lineage.
-
B.
modernStateSuccessor
Indicates that one modern state is the legal, political, or historical successor to another earlier state.
-
C.
successorFamily
Indicates that one family succeeds or follows another family in a lineage, role, position, or ownership.
-
D.
successorSystem
Indicates that one system directly follows and replaces another in function, role, or version.
-
E.
successorFoundedBy
Indicates that an entity was founded by the successor of another specified entity.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f5de508190bd6bb6d89b8952d5 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:04 p.m.