Triple
T32065455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skokomish, Washington |
E818866
|
entity |
| Predicate | locatedWithinReservationOf |
P94807
|
FINISHED |
| Object | Skokomish Indian Tribe |
E777993
|
NE 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: Skokomish Indian Tribe | Statement: [Skokomish, Washington, locatedWithinReservationOf, Skokomish Indian Tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedWithinReservationOf Context triple: [Skokomish, Washington, locatedWithinReservationOf, Skokomish Indian Tribe]
-
A.
locatedOnReservation
chosen
Indicates that an entity is situated within the geographic boundaries of a designated reservation.
-
B.
isPartOfReservation
Indicates that one entity belongs to, or is included within, a specific reservation.
-
C.
containsReservation
Indicates that one entity includes or holds a reservation associated with another entity.
-
D.
isReservationOf
Indicates that a given reservation entity is specifically associated with, or made for, a particular resource, service, or event.
-
E.
isOnReservation
Indicates that an entity is located within the boundaries of a designated reservation area.
- F. None of above.
Provenance (4 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a02145017b08190bd424cc647c08d3b |
completed | May 11, 2026, 5:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0117a6388190b82265448d23fa1a |
completed | June 14, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_6a021338e2b08190980c489ee44c18b3 |
completed | May 11, 2026, 5:34 p.m. |
Created at: May 1, 2026, 12:22 a.m.