Triple

T20026759
Position Surface form Disambiguated ID Type / Status
Subject Valdemar I of Denmark E495003 entity
Predicate placeOfDeath P21 FINISHED
Object Vordingborg 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: Vordingborg | Statement: [Valdemar I of Denmark, placeOfDeath, Vordingborg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vordingborg
Context triple: [Valdemar I of Denmark, placeOfDeath, Vordingborg]
  • A. Vordingborg chosen
    Vordingborg is a historic coastal town in southern Denmark known for the ruins of Vordingborg Castle and its prominent Goose Tower.
  • B. Svendborg
    Svendborg is a historic coastal town and seaport in southern Denmark known for its maritime heritage and location on the island of Funen.
  • C. Nyborg
    Nyborg is a historic coastal town and former royal seat in central Denmark, located on the island of Funen.
  • D. Sønderborg
    Sønderborg is a coastal town in southern Denmark known for its historic castle, waterfront setting on the island of Als, and role as a regional cultural and educational center.
  • E. Frederikshavn
    Frederikshavn is a port town in northern Jutland, Denmark, known for its ferry connections to Norway and Sweden and its maritime industry.
  • 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_69da626bfd288190aa5d65098b6433ae completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6628e1eec81908e4c9b2b0b68f0e4 completed April 20, 2026, 5:29 p.m.
Created at: April 11, 2026, 3:35 p.m.