Triple
T2732898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leven |
E60355
|
entity |
| Predicate | railStatus |
P41715
|
FINISHED |
| Object | terminus of Levenmouth rail link |
—
|
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: terminus of Levenmouth rail link | Statement: [Leven, railStatus, terminus of Levenmouth rail link]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railStatus Context triple: [Leven, railStatus, terminus of Levenmouth rail link]
-
A.
railLineStatusAfterward
Indicates the condition or operational status of a rail line after a specified event or time period has occurred.
-
B.
railwayTraffic
Indicates the presence, flow, or management of train movements along railway lines between locations.
-
C.
railwayLineUsage
Indicates how a railway line is used, such as the type or purpose of traffic or operations it supports.
-
D.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
E.
openedAsRailStop
Indicates that an entity began operation or was first established specifically as a railway stop.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaf175808190acbbb3873c7c3f67 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd968b2148190929af432c9d8001f |
completed | March 7, 2026, 7:53 a.m. |
Created at: March 6, 2026, 9:56 p.m.