Triple
T34735876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peck, Idaho |
E1001337
|
entity |
| Predicate | isWithinReservation |
P137064
|
FINISHED |
| Object | Nez Perce 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: Nez Perce Indian Reservation | Statement: [Peck, Idaho, isWithinReservation, Nez Perce Indian Reservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWithinReservation Context triple: [Peck, Idaho, isWithinReservation, Nez Perce Indian Reservation]
-
A.
isOnReservation
chosen
Indicates that an entity is located within the boundaries of a designated reservation area.
-
B.
containsReservation
Indicates that one entity includes or holds a reservation associated with another entity.
-
C.
isPartOfReservation
Indicates that one entity belongs to, or is included within, a specific reservation.
-
D.
isReservation
Indicates that one entity functions as a reservation (such as a booking or held allocation) associated with another entity.
-
E.
hasReservationIn
Indicates that an entity holds or possesses a reservation at or within a specified place, 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.