Triple
T2773532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan line |
E61513
|
entity |
| Predicate | depot |
P14646
|
FINISHED |
| Object |
Neasden Depot
Neasden Depot is a major London Underground maintenance and stabling facility serving trains on the Metropolitan line.
|
E301831
|
NE FINISHED |
How this triple was built (4 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: Neasden Depot | Statement: [Metropolitan line, depot, Neasden Depot]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neasden Depot Context triple: [Metropolitan line, depot, Neasden Depot]
-
A.
Ealing Common Depot
Ealing Common Depot is a London Underground maintenance and stabling facility serving primarily the District line in west London.
-
B.
Queens Road depot
Queens Road depot is a major tram maintenance and operations facility serving the Manchester Metrolink light rail network.
-
C.
Hammersmith depot
Hammersmith depot is a London Underground maintenance and stabling facility primarily serving the Circle and Hammersmith & City lines.
-
D.
Barking depot
Barking depot is a London Underground maintenance and stabling facility serving trains on the Hammersmith & City line.
-
E.
London Road depot
London Road depot is a maintenance and stabling facility for London Underground trains serving the Bakerloo line near Waterloo in central London.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Neasden Depot Triple: [Metropolitan line, depot, Neasden Depot]
Generated description
Neasden Depot is a major London Underground maintenance and stabling facility serving trains on the Metropolitan line.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Neasden Depot Target entity description: Neasden Depot is a major London Underground maintenance and stabling facility serving trains on the Metropolitan line.
-
A.
Ealing Common Depot
Ealing Common Depot is a London Underground maintenance and stabling facility serving primarily the District line in west London.
-
B.
Queens Road depot
Queens Road depot is a major tram maintenance and operations facility serving the Manchester Metrolink light rail network.
-
C.
Hammersmith depot
Hammersmith depot is a London Underground maintenance and stabling facility primarily serving the Circle and Hammersmith & City lines.
-
D.
Barking depot
Barking depot is a London Underground maintenance and stabling facility serving trains on the Hammersmith & City line.
-
E.
London Road depot
London Road depot is a maintenance and stabling facility for London Underground trains serving the Bakerloo line near Waterloo in central London.
- F. None of above. chosen
Provenance (5 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdd7e29e08190921fd4ac9d0679ec |
completed | March 7, 2026, 8:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afce89a144819096f9230c8d95ce3f |
completed | March 10, 2026, 7:55 a.m. |
| NEDg | Description generation | batch_69afcf7cc6f08190aefbe07ef51f1928 |
completed | March 10, 2026, 7:59 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69afcfd803848190921f73fe1b15a01b |
completed | March 10, 2026, 8:01 a.m. |
Created at: March 6, 2026, 9:57 p.m.