Triple
T28956820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maidstone East |
E731184
|
entity |
| Predicate | isInRailwayStationCategory |
P27767
|
FINISHED |
| Object | DfT category C2 |
—
|
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: DfT category C2 | Statement: [Maidstone East, isInRailwayStationCategory, DfT category C2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInRailwayStationCategory Context triple: [Maidstone East, isInRailwayStationCategory, DfT category C2]
-
A.
railwayStationCategory
chosen
Indicates the classification or type category assigned to a railway station within a rail network or system.
-
B.
isRailwayStation
Indicates that the subject is a railway station, i.e., a facility where trains regularly stop to pick up or drop off passengers and/or freight.
-
C.
railwayStationInstanceOf
Indicates that a given railway station is an instance of a specified class or type of railway station.
-
D.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
E.
isOnRailway
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65bbd8b188190bb8c1a0dbdbbccc6 |
completed | May 2, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:48 a.m.