Triple

T2989392
Position Surface form Disambiguated ID Type / Status
Subject Battle of Blenheim E80708 entity
Predicate locatedIn P40 FINISHED
Object Blindheim E80708 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: Blindheim | Statement: [Battle of Blenheim, locatedIn, Blindheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Blindheim
Context triple: [Battle of Blenheim, locatedIn, Blindheim]
  • A. Blindheim chosen
    Blindheim is a village in Bavaria, Germany, best known as the site of the pivotal 1704 Battle of Blenheim during the War of the Spanish Succession.
  • B. Waidmannslust
    Waidmannslust is a residential locality in the Reinickendorf borough of Berlin, Germany, known for its green spaces and suburban character.
  • C. Reeperbahn
    Reeperbahn is Hamburg’s famous red-light and nightlife district street, known for its clubs, bars, theaters, and vibrant entertainment scene.
  • D. Bornheim
    Bornheim is a lively residential and nightlife district in Frankfurt am Main, Germany, known for its traditional cider taverns, historic streets, and vibrant local culture.
  • E. Romanichal
    Romanichal are a subgroup of the Romani people traditionally living in Britain, known for their distinct culture, dialect, and itinerant heritage.
  • 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_69ad8b16c3488190b47b6aa7a59a335b completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad99dcdb00819092ca5f10396408e0 completed March 8, 2026, 3:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69b10900bf2481908b7742604c6d75e9 completed March 11, 2026, 6:17 a.m.
Created at: March 8, 2026, 2:59 p.m.