Triple
T18258843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dundee and Arbroath Railway |
E437290
|
entity |
| Predicate | currentUseOfRoute |
P131062
|
FINISHED |
| Object | passenger rail services |
—
|
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: passenger rail services | Statement: [Dundee and Arbroath Railway, currentUseOfRoute, passenger rail services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentUseOfRoute Context triple: [Dundee and Arbroath Railway, currentUseOfRoute, passenger rail services]
-
A.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
-
B.
usesFormerRouteOf
Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another route.
-
C.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
-
D.
routeAvailability
Indicates whether a particular route between two points is currently available for use.
-
E.
isMostCommonRouteTo
Indicates that one route is the most frequently used or typical way to reach a particular destination or outcome compared to all other possible routes.
- F. None of above. chosen
Provenance (4 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd89899c8190b8b652c4f61aa5cf |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:34 a.m.