Triple
T25864020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stoke Bank |
E651561
|
entity |
| Predicate | railwaySectionCharacter |
P147011
|
FINISHED |
| Object | downhill high‑speed section |
—
|
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: downhill high‑speed section | Statement: [Stoke Bank, railwaySectionCharacter, downhill high‑speed section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwaySectionCharacter Context triple: [Stoke Bank, railwaySectionCharacter, downhill high‑speed section]
-
A.
railwayCharacter
Indicates a relationship where an entity is characterized or defined as a railway-related figure, role, or persona.
-
B.
railwaySectionDesignatedAs
chosen
Indicates that a specific railway section has been formally assigned or classified under a particular designation or status.
-
C.
railwayLineSection
Indicates a specific segment or portion of a railway line that connects two points along the rail network.
-
D.
hasRailSymbol
Indicates that an entity is associated with or represented by a specific rail-related symbol or icon.
-
E.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 22, 2026, 8:06 a.m.