Triple
T2496747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rawtenstall railway station |
E52167
|
entity |
| Predicate | hasCarriageSidings |
P18851
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rawtenstall railway station, hasCarriageSidings, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarriageSidings Context triple: [Rawtenstall railway station, hasCarriageSidings, yes]
-
A.
hasRailFacility
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
-
B.
hasRailSystem
Indicates that an entity possesses or is served by a rail-based transportation system.
-
C.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
D.
hasRackRailway
Indicates that one entity possesses or includes a rack railway system connecting locations or operating within its area.
-
E.
hasRailYard
chosen
Indicates that one entity possesses, contains, or includes a rail yard as part of its facilities or infrastructure.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1abd3688190b5874249e1e333bc |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.