Triple
T14753592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Thameslink station |
E346674
|
entity |
| Predicate | providesServiceDirection |
P13415
|
FINISHED |
| Object | north–south cross-city |
—
|
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: north–south cross-city | Statement: [City Thameslink station, providesServiceDirection, north–south cross-city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesServiceDirection Context triple: [City Thameslink station, providesServiceDirection, north–south cross-city]
-
A.
serviceDirection
chosen
Indicates the direction or orientation in which a service is provided or operates relative to involved entities.
-
B.
servedByDirection
Indicates that something (such as a route, service, or facility) is provided or accessed in a specific directional orientation (e.g., northbound, inbound).
-
C.
providesServiceTowards
Indicates that one entity delivers or performs a service directed to or for the benefit of another entity.
-
D.
servesDirection
Indicates that one entity provides service or functionality oriented toward, or in the direction of, another entity.
-
E.
providesServices
Indicates that one entity supplies or performs services for the benefit or use of 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d59df08190a86da5048358bd6e |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.