Triple
T28428223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoshone-Paiute Tribes of the Duck Valley Reservation |
E715047
|
entity |
| Predicate | reservationSpans |
P80084
|
FINISHED |
| Object | Nevada |
—
|
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: Nevada | Statement: [Shoshone-Paiute Tribes of the Duck Valley Reservation, reservationSpans, Nevada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservationSpans Context triple: [Shoshone-Paiute Tribes of the Duck Valley Reservation, reservationSpans, Nevada]
-
A.
reservationAlsoIn
Indicates that a reservation is additionally included or valid in another context, system, or location beyond its primary one.
-
B.
reservationIn
Indicates that a reservation is associated with, or booked for, a specific place, service, or resource.
-
C.
reservationEnclosedBy
Indicates that one reservation is fully contained within the spatial or logical boundaries of another reservation.
-
D.
reservationProvision
Indicates that one entity provides, allocates, or sets aside a reservation (such as a booked resource, service slot, or capacity) for another entity.
-
E.
reservationScope
chosen
Indicates the extent or range within which a reservation applies or is valid.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:38 a.m.