Triple
T24994961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne tram route 3 |
E625543
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Melbourne tram route |
C49654
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Melbourne tram route Context triple: [Melbourne tram route 3, instanceOf, Melbourne tram route]
-
A.
Yarra Trams service
A Yarra Trams service is an individual scheduled tram journey operated on Melbourne’s tram network, defined by its route, timetable, and vehicle providing passenger transport between designated stops.
-
B.
Sheffield Supertram route
A Sheffield Supertram route is a defined public transport service path within the Sheffield light rail network, specifying the sequence of stops, track segments, and operational patterns followed by trams between termini.
-
C.
trolleybus line
A trolleybus line is a designated public transit route served by electrically powered buses that draw current from overhead wires along the roadway.
-
D.
Sydney Trains station
A Sydney Trains station is a designated rail facility within the Sydney Trains network where passengers can access, board, alight from, and interchange between suburban train services and related transport modes.
-
E.
London Tramlink route
A London Tramlink route is a designated service path within the Tramlink light rail network in South London, defined by its specific sequence of stops, operating pattern, and timetable.
- F. None of above. chosen
Provenance (1 batch)
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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:04 a.m.