Triple
T24361812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Barnet |
E614080
|
entity |
| Predicate | railwayStationManagedBy |
P44064
|
FINISHED |
| Object | Great Northern |
—
|
NE NERFINISHED |
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: Great Northern | Statement: [New Barnet, railwayStationManagedBy, Great Northern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayStationManagedBy Context triple: [New Barnet, railwayStationManagedBy, Great Northern]
-
A.
isRailwayStationInNetwork
Indicates that a railway station belongs to, and is served as part of, a particular railway network.
-
B.
hasRailwayStationRole
Indicates that an entity holds or is assigned a specific functional role or capacity within the operation or management of a railway station.
-
C.
railwayControlledBy
chosen
Indicates that the operation, management, or authority over a railway is exercised by a specified controlling entity.
-
D.
hasRailwayStationOn
Indicates that a railway station is located on or serves a particular railway line, route, or network segment.
-
E.
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.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29384a2f88190885eb141c5c44a2d |
completed | April 29, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2 a.m.