Triple
T32505292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch Shiel |
E830773
|
entity |
| Predicate | hasNearbyRailwayViaduct |
P199704
|
FINISHED |
| Object | Glenfinnan Viaduct |
—
|
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: Glenfinnan Viaduct | Statement: [Loch Shiel, hasNearbyRailwayViaduct, Glenfinnan Viaduct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyRailwayViaduct Context triple: [Loch Shiel, hasNearbyRailwayViaduct, Glenfinnan Viaduct]
-
A.
hasNearbyRailway
Indicates that one entity is located close to a railway associated with or relevant to another entity.
-
B.
hasViaduct
Indicates that one entity possesses, includes, or is connected by a viaduct in relation to another entity.
-
C.
hasNearbyRailwayStation
Indicates that a railway station is located within a short or convenient distance from the referenced entity.
-
D.
hasNearbyBridge
Indicates that one entity is located close to a bridge associated with or relevant to it.
-
E.
hasRailwayTunnel
Indicates that one entity contains, includes, or is connected by a railway tunnel associated with the other entity.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69ff519a67008190b1eda931fdeff53e |
completed | May 9, 2026, 3:24 p.m. |
Created at: May 1, 2026, 1 a.m.