Triple
T27209802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanblee, South Dakota |
E683966
|
entity |
| Predicate | liesWithinReservation |
P137064
|
FINISHED |
| Object | Pine Ridge Indian 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: Pine Ridge Indian Reservation | Statement: [Wanblee, South Dakota, liesWithinReservation, Pine Ridge Indian Reservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesWithinReservation Context triple: [Wanblee, South Dakota, liesWithinReservation, Pine Ridge Indian Reservation]
-
A.
containsReservation
Indicates that one entity includes or holds a reservation associated with another entity.
-
B.
isPartOfReservation
Indicates that one entity belongs to, or is included within, a specific reservation.
-
C.
isOnReservation
chosen
Indicates that an entity is located within the boundaries of a designated reservation area.
-
D.
isReservationOf
Indicates that a given reservation entity is specifically associated with, or made for, a particular resource, service, or event.
-
E.
isReservation
Indicates that one entity functions as a reservation (such as a booking or held allocation) associated with another 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625e8342c8190a809bfb169967a89 |
completed | May 2, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:39 a.m.