Triple
T2790314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern line |
E61912
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Bank station |
E283368
|
NE 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: Bank station | Statement: [Northern line, passesThrough, Bank station]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bank station Context triple: [Northern line, passesThrough, Bank station]
-
A.
Bank station
chosen
Bank station is a major central London interchange on the Underground and Docklands Light Railway network, serving as a key hub in the City of London financial district.
-
B.
Bay station
Bay station is a Toronto subway station located in the downtown area, serving the Bloor–Danforth line and providing access to the upscale Yorkville neighborhood.
-
C.
Salaryevo station
Salaryevo station is a Moscow Metro station on the Sokolnicheskaya Line serving the southwestern outskirts of the city.
-
D.
King station
King station is a downtown Toronto subway station on the TTC network serving the Financial District and nearby attractions.
-
E.
Legarda station
Legarda station is an elevated rapid transit stop on Manila’s LRT Line 2 serving the Sampaloc area and nearby universities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddb4ef3081909122840a357801bf |
completed | March 7, 2026, 8:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afc65c1f848190b6efeefb64a3e131 |
completed | March 10, 2026, 7:21 a.m. |
Created at: March 6, 2026, 9:58 p.m.