Triple
T11607388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-68 tram |
E275296
|
entity |
| Predicate | replacedBy |
P101
|
FINISHED |
| Object | M5000 tram |
E35104
|
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: M5000 tram | Statement: [T-68 tram, replacedBy, M5000 tram]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M5000 tram Context triple: [T-68 tram, replacedBy, M5000 tram]
-
A.
M5000 tram
chosen
The M5000 tram is a modern light-rail vehicle used across the Manchester Metrolink network as its primary fleet for urban passenger services.
-
B.
SL95 tram
The SL95 tram is a high-floor, bi-directional tram model used in Oslo, Norway, known for its large capacity and operation on the city’s light rail and tram network.
-
C.
Tram 2000
Tram 2000 is a series of articulated light rail vehicles used for urban public transport in Zürich, Switzerland.
-
D.
T-68 tram
The T-68 tram was a type of light rail vehicle used on Greater Manchester’s Metrolink system in the UK before being replaced by newer models.
-
E.
Bombardier Flexity trams
Bombardier Flexity trams are a family of modern, low-floor light rail vehicles designed for urban public transport systems worldwide.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89551649c81908096ff392677442d |
completed | April 10, 2026, 6:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e8a82381708190aa0e674603d5778a |
completed | April 22, 2026, 10:51 a.m. |
Created at: April 8, 2026, 9:38 p.m.