Triple
T19450001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fell centre rail system |
E486590
|
entity |
| Predicate | railPosition |
P135934
|
FINISHED |
| Object | between running rails |
—
|
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: between running rails | Statement: [Fell centre rail system, railPosition, between running rails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railPosition Context triple: [Fell centre rail system, railPosition, between running rails]
-
A.
trainPosition
Indicates the spatial location or coordinates of a train along its route or track at a given time.
-
B.
rackPosition
Indicates the spatial placement or slot of an item within a rack or racking system.
-
C.
positionInTrain
Indicates the relative location or ordering of an entity within the sequence of cars or sections that make up a train.
-
D.
railHead
Indicates a relationship where one location serves as the terminus or primary endpoint of a railway line for another location or transport link.
-
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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338caeb48190aeb1d511996984e3 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.