Triple
T187858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El |
E4021
|
entity |
| Predicate | hasRouteOrientation |
P4069
|
FINISHED |
| Object | east–west |
—
|
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: east–west | Statement: [El, hasRouteOrientation, east–west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteOrientation Context triple: [El, hasRouteOrientation, east–west]
-
A.
hasCommuterOrientation
Indicates that an entity is designed or intended primarily for use by commuters, emphasizing suitability for regular travel between home and work or study.
-
B.
hasTrafficDirection
chosen
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
C.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
D.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
E.
hasEasiestRoute
Indicates that one entity provides or represents the simplest or least difficult route or path to reach another entity or destination.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2594940e48190a3d8efbce46241c3 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25670feb081908e26a2543ebe7b3a |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.