Triple
T8967191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mornington Crescent tube station |
E214167
|
entity |
| Predicate | servedDirection |
P48943
|
FINISHED |
| Object | northbound Northern line |
—
|
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: northbound Northern line | Statement: [Mornington Crescent tube station, servedDirection, northbound Northern line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedDirection Context triple: [Mornington Crescent tube station, servedDirection, northbound Northern line]
-
A.
servedByDirection
chosen
Indicates that something (such as a route, service, or facility) is provided or accessed in a specific directional orientation (e.g., northbound, inbound).
-
B.
servesDirection
Indicates that one entity provides service or functionality oriented toward, or in the direction of, another entity.
-
C.
servedDestination
Indicates that a service or action is directed toward, or provided to, a particular destination.
-
D.
serviceDirection
Indicates the direction or orientation in which a service is provided or operates relative to involved entities.
-
E.
servedFrom
Indicates that something is provided, delivered, or made available from a particular source or location.
- 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc676389948190aa78fdf6a5ae74a5 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:01 p.m.