Triple
T28435073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland–Lincoln City travel corridor |
E715239
|
entity |
| Predicate | hasEndingCity |
P26386
|
FINISHED |
| Object | Lincoln City, 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: Lincoln City, Oregon | Statement: [Portland–Lincoln City travel corridor, hasEndingCity, Lincoln City, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndingCity Context triple: [Portland–Lincoln City travel corridor, hasEndingCity, Lincoln City, Oregon]
-
A.
hasPilgrimageDestinationAtEnd
Indicates that an entity’s journey or process culminates at a specific location regarded as its pilgrimage destination.
-
B.
hasIntermediateCity
Indicates that there is a city located between two other places along a route or connection.
-
C.
hasEndpointCity
chosen
Indicates that a route, connection, or path terminates at a particular city as one of its endpoints.
-
D.
finalCity
Indicates that a given city is the last or ultimate city associated with an entity within a sequence, process, or journey.
-
E.
hasCityPair
Indicates a relationship that links two cities considered as a connected or associated pair, often for purposes such as travel, trade, or comparison.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 28, 2026, 1:42 a.m.