Triple

T2759288
Position Surface form Disambiguated ID Type / Status
Subject Battle of Copenhagen (1801) E61180 entity
Predicate location P40 FINISHED
Object Øresund E70875 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: Øresund | Statement: [Battle of Copenhagen (1801), location, Øresund]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Øresund
Context triple: [Battle of Copenhagen (1801), location, Øresund]
  • A. Øresund chosen
    Øresund is the strait between Denmark and Sweden that connects the Baltic Sea to the North Sea and is spanned by the Øresund Bridge.
  • B. Kattegat
    Kattegat is a shallow sea area and strait between Denmark and Sweden that forms a key maritime passage linking the North Sea with the Baltic Sea.
  • C. Great Belt
    The Great Belt is a major strait in Denmark that separates the islands of Funen and Zealand and connects the Baltic Sea to the Kattegat.
  • D. Skagerrak
    Skagerrak is a strait and sea area between Norway, Denmark, and Sweden that connects the North Sea to the Baltic Sea.
  • E. Bothnian Sea
    The Bothnian Sea is the southern part of the Gulf of Bothnia, a brackish water basin between Sweden and Finland that forms a northern arm of the Baltic Sea.
  • 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_69ab4b7a85bc819094a349b84beb1f2c completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdb8d34f88190a760111fe303cf24 completed March 7, 2026, 8:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69afbbe2d9cc81909b041635ae793bc3 completed March 10, 2026, 6:36 a.m.
Created at: March 6, 2026, 9:57 p.m.