Triple
T26592057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosebud Sioux Tribe |
E667383
|
entity |
| Predicate | borderedByReservation |
P224
|
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: [Rosebud Sioux Tribe, borderedByReservation, Pine Ridge Indian Reservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedByReservation Context triple: [Rosebud Sioux Tribe, borderedByReservation, Pine Ridge Indian Reservation]
-
A.
borderedBy
chosen
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
borderIssue
Indicates a dispute, conflict, or problem related to the definition, control, or management of a boundary between two or more entities.
-
C.
reservationEnclosedBy
Indicates that one reservation is fully contained within the spatial or logical boundaries of another reservation.
-
D.
borderDefinedBetween
Indicates that a boundary line or border is formally established between two geographic or political entities.
-
E.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 27, 2026, 2:08 a.m.