Triple
T28435072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland–Lincoln City travel corridor |
E715239
|
entity |
| Predicate | hasStartingCity |
P22794
|
FINISHED |
| Object | Portland, 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: Portland, Oregon | Statement: [Portland–Lincoln City travel corridor, hasStartingCity, Portland, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartingCity Context triple: [Portland–Lincoln City travel corridor, hasStartingCity, Portland, Oregon]
-
A.
startCity
chosen
Indicates the city where a journey, route, or transportation service begins.
-
B.
hasTargetCity
Indicates that something is directed toward, intended for, or specifically associated with a particular city as its target.
-
C.
hasStartLandmark
Indicates that an entity begins, originates, or is initially located at a specified landmark.
-
D.
hasIntermediateCity
Indicates that there is a city located between two other places along a route or connection.
-
E.
hasGatewayCity
Indicates that one place serves as the primary gateway city (main entry or transit hub) for accessing another place.
- 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_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 28, 2026, 1:42 a.m.