Triple
T31907433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pwllheli railway station |
E814590
|
entity |
| Predicate | lineEndDirection |
P3384
|
FINISHED |
| Object | western terminus |
—
|
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: western terminus | Statement: [Pwllheli railway station, lineEndDirection, western terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineEndDirection Context triple: [Pwllheli railway station, lineEndDirection, western terminus]
-
A.
lineTerminusDirection
chosen
Indicates the directional orientation or bearing at which a line segment or route terminates at its endpoint.
-
B.
branchLineDirection
Indicates the directional orientation or flow of a branch line relative to a main line or reference point.
-
C.
lineDirectionTo
Indicates the directional relationship from one line to another, such as whether they point in the same, opposite, or a specific relative direction.
-
D.
lineOrientation
Indicates the directional alignment or angle of a line relative to a reference frame or axis.
-
E.
linePositioning
Indicates how one line is spatially arranged or oriented in relation to another line.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, midnight