Triple
T751542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland International Airport station |
E15458
|
entity |
| Predicate | hasWayfinding |
P8170
|
FINISHED |
| Object | airport and TriMet wayfinding signs |
—
|
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: airport and TriMet wayfinding signs | Statement: [Portland International Airport station, hasWayfinding, airport and TriMet wayfinding signs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWayfinding Context triple: [Portland International Airport station, hasWayfinding, airport and TriMet wayfinding signs]
-
A.
hasNavigationAid
chosen
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
B.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
C.
portalLocation
Indicates that a portal is situated at or associated with a specific location.
-
D.
navigationArea
Indicates that a specified region or space is designated for movement, routing, or pathfinding within an environment.
-
E.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64c67748190aef3522b4b428563 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a501c4cc81908de6d63e3d4f60d7 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.