Triple
T27563427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeastern Metro services |
E695832
|
entity |
| Predicate | majorLondonTerminus |
P24452
|
FINISHED |
| Object | London Charing Cross |
—
|
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: London Charing Cross | Statement: [Southeastern Metro services, majorLondonTerminus, London Charing Cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorLondonTerminus Context triple: [Southeastern Metro services, majorLondonTerminus, London Charing Cross]
-
A.
primaryLondonTerminal
chosen
Indicates that a given station serves as the main London terminal for a particular rail service or route.
-
B.
secondaryLondonTerminal
Indicates that a location serves as a secondary terminal in London associated with a primary London terminal for a given service or route.
-
C.
originalLondonTerminusLocation
Indicates the location of an entity’s original terminus station in London.
-
D.
hasLondonUndergroundStation
Indicates that a place or area contains at least one London Underground (Tube) station within its boundaries.
-
E.
endStationOnCentralLine
Indicates that a station serves as a terminal (end) station on the Central Line.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 27, 2026, 1:40 p.m.