Triple
T15928494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyon tram line T2 |
E386264
|
entity |
| Predicate | usesRollingStock |
P5426
|
FINISHED |
| Object | Citadis 302 |
E1169860
|
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: Citadis 302 | Statement: [Lyon tram line T2, usesRollingStock, Citadis 302]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Citadis 302 Context triple: [Lyon tram line T2, usesRollingStock, Citadis 302]
-
A.
Citadis 302
chosen
The Citadis 302 is a low-floor, modular light rail tram model from Alstom’s Citadis family, widely used in urban tramway systems around the world.
-
B.
Citadis 502
The Citadis 502 is a variant of Alstom’s Citadis low-floor light rail vehicles, designed for modern urban tramway systems with modular, customizable configurations.
-
C.
Citadis 402
The Citadis 402 is a low-floor, multi-section light rail tram model produced by Alstom for modern urban transit systems.
-
D.
Citadis 304
The Citadis 304 is a low-floor light rail tram model produced by Alstom for modern urban public transport networks.
-
E.
Citadis 403
The Citadis 403 is a low-floor light rail tram model from Alstom’s Citadis family, designed for modern urban transit systems with high passenger capacity and modular configuration.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156a39abc8190927818f6e185033a |
completed | April 16, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb5b0833081909668c042234b5b75 |
completed | May 9, 2026, 10:31 p.m. |
Created at: April 10, 2026, 4:52 a.m.