Triple
T29257391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley Falls, Oregon |
E741738
|
entity |
| Predicate | isStopoverPoint |
P166780
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Valley Falls, Oregon, isStopoverPoint, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStopoverPoint Context triple: [Valley Falls, Oregon, isStopoverPoint, true]
-
A.
isStopoverSiteFor
Indicates that a location serves as a temporary stopping or resting point along the route or journey of another entity.
-
B.
hasStopoverState
Indicates that an entity’s journey or process includes an intermediate stop or temporary state before reaching its final destination or outcome.
-
C.
stopoverLocation
Indicates that an entity makes an intermediate stop or layover at a specified location during a journey or route.
-
D.
stopoverAirport
Indicates that an itinerary or flight includes a particular airport as an intermediate stop between the origin and final destination.
-
E.
isPassengerStop
Indicates that a location serves as a designated place where passengers may board or alight from a vehicle or transport service.
- F. None of above. chosen
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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664af8ca48190bfd74d02b761a1b4 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661e9cb308190a56e25dc17df248e |
completed | May 2, 2026, 8:43 p.m. |
Created at: April 28, 2026, 12:38 p.m.