Triple
T32537499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deeside Line |
E831627
|
entity |
| Predicate | routeNowUsedAs |
P131062
|
FINISHED |
| Object | long-distance footpath |
—
|
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: long-distance footpath | Statement: [Deeside Line, routeNowUsedAs, long-distance footpath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeNowUsedAs Context triple: [Deeside Line, routeNowUsedAs, long-distance footpath]
-
A.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
B.
currentUseOfRoute
chosen
Indicates that a particular route is presently being used for a specific purpose, activity, or traffic flow.
-
C.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
D.
routeChoiceIn
Indicates that a particular route is selected or used within a given route choice or decision context.
-
E.
routeAlong
Indicates that one entity follows, runs parallel to, or is situated along the course or path defined by another entity.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c572f79c819095c549d8c9942b3a |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:01 a.m.