Triple
T7145741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge of Weir |
E166562
|
entity |
| Predicate | railwayLineNow |
P75094
|
FINISHED |
| Object | part of National Cycle Route 75 |
—
|
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: part of National Cycle Route 75 | Statement: [Bridge of Weir, railwayLineNow, part of National Cycle Route 75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayLineNow Context triple: [Bridge of Weir, railwayLineNow, part of National Cycle Route 75]
-
A.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
B.
railwayLineUsage
Indicates how a railway line is used, such as the type or purpose of traffic or operations it supports.
-
C.
railLineOrigin
Indicates that a rail line begins or originates from a specified location or point.
-
D.
railLineStatusAfterward
Indicates the condition or operational status of a rail line after a specified event or time period has occurred.
-
E.
railStatus
Indicates the current operational condition or state of a rail-related entity (such as a track, line, or service) within the system.
- 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7d3c48c8190a71a61a1d50cd7da |
completed | March 27, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:46 p.m.