Triple
T2148976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leeds railway station |
E47134
|
entity |
| Predicate | isConnectedToAirportByRail |
P3791
|
FINISHED |
| Object | Leeds Bradford Airport bus links |
—
|
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: Leeds Bradford Airport bus links | Statement: [Leeds railway station, isConnectedToAirportByRail, Leeds Bradford Airport bus links]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConnectedToAirportByRail Context triple: [Leeds railway station, isConnectedToAirportByRail, Leeds Bradford Airport bus links]
-
A.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
B.
hasMajorRailLinksTo
Indicates that there are significant railway connections or routes between two locations.
-
C.
hasRailwayStation
Indicates that a place or location is served by, or contains, a railway station.
-
D.
connectsWithAirport
Indicates that there is a direct transportation or operational link established between an entity and an airport.
-
E.
hasPublicTransportConnection
chosen
Indicates that there is an available public transportation link or service connecting the related entities.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeaa14bc81908486683decd7ae42 |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9846e88190b6c2941dd9ce7749 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.