Triple

T14868758
Position Surface form Disambiguated ID Type / Status
Subject Love Parade E349684 entity
Predicate heldInCity P7898 FINISHED
Object Dortmund E162155 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: Dortmund | Statement: [Love Parade, heldInCity, Dortmund]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dortmund
Context triple: [Love Parade, heldInCity, Dortmund]
  • A. Dortmund chosen
    Dortmund is a major city in western Germany known for its rich football culture, industrial heritage, and home club Borussia Dortmund.
  • B. Mönchengladbach
    Mönchengladbach is a city in western Germany known for its textile industry heritage and its football club Borussia Mönchengladbach.
  • C. Düsseldorf
    Düsseldorf is a major German city on the Rhine River known for its fashion and art scenes, modern architecture, and status as an important economic and financial center.
  • D. Duisburg
    Duisburg is a major industrial and port city in western Germany’s Ruhr region, known for its steel production and one of the world’s largest inland harbors.
  • E. Wolfsburg
    Wolfsburg is a German city best known as the headquarters and main production site of the Volkswagen automobile company.
  • 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_69d822ee4f408190b6ac3b2fa434f0df completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded5776b848190bfe3a06ff261dc31 completed April 15, 2026, 12:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff9976bc888190a050c2502d1f8e81 completed May 9, 2026, 8:30 p.m.
Created at: April 10, 2026, 1:55 a.m.