Triple
T26517244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mellette County, South Dakota |
E669851
|
entity |
| Predicate | hasReservationLand |
P82476
|
FINISHED |
| Object | Rosebud 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: Rosebud Indian Reservation | Statement: [Mellette County, South Dakota, hasReservationLand, Rosebud Indian Reservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReservationLand Context triple: [Mellette County, South Dakota, hasReservationLand, Rosebud Indian Reservation]
-
A.
hasReserveLand
chosen
Indicates that an entity possesses or is allocated a designated area of land set aside as a reserve.
-
B.
hasReservationOf
Indicates that one entity holds or possesses a reservation for another entity (such as a service, resource, or event).
-
C.
hasReservationIn
Indicates that an entity holds or possesses a reservation at or within a specified place, service, or event.
-
D.
isReservationOf
Indicates that a given reservation entity is specifically associated with, or made for, a particular resource, service, or event.
-
E.
hasReservationFor
Indicates that an entity holds or is associated with a reservation for a specific event, service, or resource.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: April 27, 2026, 1:24 a.m.