Triple
T34791084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barca d'Alva |
E1002945
|
entity |
| Predicate | railConnectionDirection |
P120426
|
FINISHED |
| Object | west to Porto |
—
|
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: west to Porto | Statement: [Barca d'Alva, railConnectionDirection, west to Porto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railConnectionDirection Context triple: [Barca d'Alva, railConnectionDirection, west to Porto]
-
A.
railwayRouteDirection
chosen
Indicates the direction or orientation in which a railway route runs or is intended to be traveled.
-
B.
railConnectionPurpose
Indicates the intended function or goal of a particular rail connection between locations or networks.
-
C.
railwayTrafficDirection
Indicates the customary side of the track on which trains are operated or expected to run within a given railway system or segment.
-
D.
terminusDirection
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
E.
providesRailConnectionsWithin
Indicates that an entity offers or facilitates rail transport links connecting locations inside a specified area or region.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.