Triple

T5870172
Position Surface form Disambiguated ID Type / Status
Subject Dynamo Dresden E130495 entity
Predicate nickname P55 FINISHED
Object Dynamo E455991 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: Dynamo | Statement: [Dynamo Dresden, nickname, Dynamo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dynamo
Context triple: [Dynamo Dresden, nickname, Dynamo]
  • A. Dynamo
    Dynamo is a prominent Russian sports club based in Moscow, best known for its professional football and ice hockey teams.
  • B. Dynamo chosen
    Dynamo is the commonly used nickname for FC Dynamo Kyiv, one of Ukraine’s most successful and historically significant football clubs.
  • C. Dynamo Diesel
    Dynamo Diesel is the bull-themed official mascot of the Houston Dynamo Major League Soccer team, known for energizing fans at matches and community events.
  • D. Dyme
    Dyme was an ancient Greek city-state in the region of Achaea, known as one of its earliest and westernmost poleis.
  • E. Pylon
    Pylon was an influential American post-punk band from Athens, Georgia, known for its angular guitar sound and role in the early alternative rock scene.
  • 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_69c0085047dc8190af24e311edad3c07 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c035f6b8548190a58971b05869228d completed March 22, 2026, 6:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0a1d39dd081908d77ee82c24178cf completed March 23, 2026, 2:13 a.m.
Created at: March 22, 2026, 3:56 p.m.