Triple
T27310344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standing Rock Sioux Tribe |
E689185
|
entity |
| Predicate | hasReservationBorder |
P197697
|
FINISHED |
| Object | Missouri River |
—
|
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: Missouri River | Statement: [Standing Rock Sioux Tribe, hasReservationBorder, Missouri River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReservationBorder Context triple: [Standing Rock Sioux Tribe, hasReservationBorder, Missouri River]
-
A.
hasReservationIn
Indicates that an entity holds or possesses a reservation at or within a specified place, service, or event.
-
B.
containsReservation
Indicates that one entity includes or holds a reservation associated with another entity.
-
C.
hasReservationFor
Indicates that an entity holds or is associated with a reservation for a specific event, service, or resource.
-
D.
hasReservationArea
Indicates that an entity is assigned or associated with a specific reserved area or section designated for its use.
-
E.
hasReservationOf
Indicates that one entity holds or possesses a reservation for another entity (such as a service, resource, or event).
- F. None of above. chosen
Provenance (4 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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fea2cfcd648190a15e5b90889095b1 |
completed | May 9, 2026, 2:58 a.m. |
Created at: April 27, 2026, 11:27 a.m.