Triple
T22312107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buffalo County, South Dakota |
E551541
|
entity |
| Predicate | hasReservationLands |
P82476
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
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: yes | Statement: [Buffalo County, South Dakota, hasReservationLands, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReservationLands Context triple: [Buffalo County, South Dakota, hasReservationLands, yes]
-
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.
hasReservationFor
Indicates that an entity holds or is associated with a reservation for a specific event, service, or resource.
-
E.
isReservationOf
Indicates that a given reservation entity is specifically associated with, or made for, a particular resource, service, or event.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1574f97cc81909685aeef15d02af9 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.