Triple
T36531170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siletz Dee-ni language |
E900446
|
entity |
| Predicate | belongsToReservation |
P115898
|
FINISHED |
| Object | Siletz 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: Siletz Reservation | Statement: [Siletz Dee-ni language, belongsToReservation, Siletz Reservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToReservation Context triple: [Siletz Dee-ni language, belongsToReservation, Siletz Reservation]
-
A.
associatedWithReservation
Indicates that one entity has a connection or linkage to a specific reservation.
-
B.
isPartOfReservation
chosen
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.
hasReservationRole
Indicates that an entity holds a specific role or function within the context of a reservation.
- 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
Created at: May 3, 2026, 4:11 p.m.