Triple
T24092999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umatilla |
E596838
|
entity |
| Predicate | reservationHeadquarters |
P17490
|
FINISHED |
| Object | Mission, Oregon |
—
|
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: Mission, Oregon | Statement: [Umatilla, reservationHeadquarters, Mission, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservationHeadquarters Context triple: [Umatilla, reservationHeadquarters, Mission, Oregon]
-
A.
headquartersAt
Indicates that an organization’s main administrative center or primary office is located at a specified place.
-
B.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
C.
headquartersFor
chosen
Indicates that a location serves as the main administrative center or base of operations for an organization or entity.
-
D.
finalHeadquarters
Indicates the location that ultimately serves as an entity’s last or definitive headquarters.
-
E.
nearHeadquartersOf
Indicates that one entity is located geographically close to the headquarters of another entity.
- 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_69e288c548048190a5c1018da1166a21 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd221ebc8190801fa6c08987c126 |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:57 p.m.