Triple

T21963331
Position Surface form Disambiguated ID Type / Status
Subject Red Line (Stockholm metro) E542391 entity
Predicate hasRollingStock P1305 FINISHED
Object C30 train NE NERFINISHED

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: C30 train | Statement: [Red Line (Stockholm metro), hasRollingStock, C30 train]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: C30 train
Context triple: [Red Line (Stockholm metro), hasRollingStock, C30 train]
  • A. C30 trains chosen
    C30 trains are a modern fleet of metro cars introduced to upgrade and expand passenger service on Stockholm’s Green line.
  • B. MX3000 train
    The MX3000 train is a modern electric multiple unit used as the primary passenger rolling stock on the Oslo Metro system in Norway.
  • C. C train
    The C train is a local service on the New York City Subway’s Eighth Avenue Line, running primarily between Upper Manhattan and Brooklyn.
  • D. DT3 train
    The DT3 train is a type of electric multiple unit specifically designed for and operated on the Nuremberg U-Bahn rapid transit system in Germany.
  • E. 3 train
    The 3 train is a New York City Subway service that runs on the IRT Lenox Avenue and Eastern Parkway Lines, connecting Manhattan and Brooklyn.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c47fab1081908dc74a6545dbb051 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f12458e4488190a04f8d3958854b49 completed April 28, 2026, 9:19 p.m.
Created at: April 16, 2026, 8:01 p.m.