Triple
T38535155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Gorge AVA |
E923476
|
entity |
| Predicate | statePart |
P115061
|
FINISHED |
| Object | northern Oregon |
—
|
LITERAL 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: northern Oregon | Statement: [Columbia Gorge AVA, statePart, northern Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statePart Context triple: [Columbia Gorge AVA, statePart, northern Oregon]
-
A.
stateOrRegion
chosen
Indicates that one entity is a state or region in which the other entity is located or with which it is associated.
-
B.
servesPartOfState
Indicates that an entity serves as an official or functional part of a larger state-level governmental or administrative structure.
-
C.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
-
D.
stateUnit
Indicates a relationship where one entity is a constituent administrative or organizational unit within a larger state or state-like structure.
-
E.
statePartner
Indicates that two entities are formally partnered or allied at the level of state or governmental institutions.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:32 p.m.