Triple

T20314733
Position Surface form Disambiguated ID Type / Status
Subject Hamburg–Copenhagen E510349 entity
Predicate usesRollingStock P5426 FINISHED
Object DSB IC3 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: DSB IC3 | Statement: [Hamburg–Copenhagen, usesRollingStock, DSB IC3]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: DSB IC3
Context triple: [Hamburg–Copenhagen, usesRollingStock, DSB IC3]
  • A. DSB
    DSB is the commonly used abbreviation for the World Trade Organization’s Dispute Settlement Body, which oversees the resolution of trade disputes between member countries.
  • B. DSB
    DSB is Norway’s national authority responsible for civil protection, emergency preparedness, and accident prevention.
  • C. DSB chosen
    DSB is Denmark’s national railway company, responsible for operating most passenger train services across the country.
  • D. DSO
    DSO is a British military decoration awarded to officers for distinguished service in combat, typically in leadership roles.
  • E. DSO
    DSO is the commonly used abbreviation for the Dallas Symphony Orchestra, a major American symphony orchestra based in Dallas, Texas.
  • 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_69e0b4c7491c8190961113c4283b10b0 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e67786f4dc8190b02a6c2a4338362d completed April 20, 2026, 6:59 p.m.
Created at: April 16, 2026, 11:19 a.m.