Triple
T31640718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch Eil |
E807446
|
entity |
| Predicate | railwayStationOnShore |
P180657
|
FINISHED |
| Object | Loch Eil Outward Bound railway station |
—
|
NE NERFINISHED |
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: Loch Eil Outward Bound railway station | Statement: [Loch Eil, railwayStationOnShore, Loch Eil Outward Bound railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayStationOnShore Context triple: [Loch Eil, railwayStationOnShore, Loch Eil Outward Bound railway station]
-
A.
railwayStationFor
Indicates a relationship where a railway station serves, is designated for, or primarily associated with a particular place, line, or service.
-
B.
hasRailwayStation
Indicates that a place or location is served by, or contains, a railway station.
-
C.
hasRailwayStationOn
Indicates that a railway station is located on or serves a particular railway line, route, or network segment.
-
D.
railwayStationFeature
Indicates that a railway station possesses or is characterized by a particular feature, facility, or attribute.
-
E.
railTerminus
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 30, 2026, 10:49 p.m.