Triple
T34148295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shannon County, South Dakota |
E875923
|
entity |
| Predicate | reservationCountyFor |
P178687
|
FINISHED |
| Object | Oglala Sioux Tribe |
—
|
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: Oglala Sioux Tribe | Statement: [Shannon County, South Dakota, reservationCountyFor, Oglala Sioux Tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservationCountyFor Context triple: [Shannon County, South Dakota, reservationCountyFor, Oglala Sioux Tribe]
-
A.
reservationIn
Indicates that a reservation is associated with, or booked for, a specific place, service, or resource.
-
B.
reservationNear
Indicates that a reservation is located geographically close to a specified reference entity or place.
-
C.
reservationAlsoIn
Indicates that a reservation is additionally included or valid in another context, system, or location beyond its primary one.
-
D.
reservationEstablishedIn
Indicates that a reservation (such as a booking or protected area) was created, set up, or formally established in a particular place or context.
-
E.
reservationEnclosedBy
Indicates that one reservation is fully contained within the spatial or logical boundaries of another reservation.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f713bfdc148190a249a7874320bab8 |
completed | May 3, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f7135fa2988190a20a94cfe616d754 |
completed | May 3, 2026, 9:20 a.m. |
Created at: May 1, 2026, 1:54 a.m.