Triple
T32537652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London King’s Cross – Edinburgh Waverley |
E831631
|
entity |
| Predicate | alsoServedByOperator |
P64555
|
FINISHED |
| Object | Lumo |
—
|
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: Lumo | Statement: [London King’s Cross – Edinburgh Waverley, alsoServedByOperator, Lumo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoServedByOperator Context triple: [London King’s Cross – Edinburgh Waverley, alsoServedByOperator, Lumo]
-
A.
alsoServedBy
Indicates that the same service, function, or role is additionally provided or fulfilled by another entity alongside the primary one.
-
B.
alsoOperatedBy
chosen
Indicates that an entity is additionally operated or managed by another operator, alongside any primary or other operators.
-
C.
alsoOperatesIn
Indicates that an entity, in addition to its primary location or domain, conducts operations or activities in another specified place or context.
-
D.
associatedLineOperator
Indicates that an entity is linked to, managed by, or otherwise connected with a specific line operator.
-
E.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c572f79c819095c549d8c9942b3a |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:01 a.m.