Triple

T20824001
Position Surface form Disambiguated ID Type / Status
Subject Tejn E512647 entity
Predicate connectedTo P37 FINISHED
Object Gudhjem 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: Gudhjem | Statement: [Tejn, connectedTo, Gudhjem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gudhjem
Context triple: [Tejn, connectedTo, Gudhjem]
  • A. Gudhjem chosen
    Gudhjem is a picturesque coastal village on the Danish island of Bornholm, known for its steep streets, red-roofed houses, and harbor overlooking the Baltic Sea.
  • B. Haderup
    Haderup is a small town in Denmark, known locally as a rural community that gave its name to the former Aulum-Haderup Municipality.
  • C. Hedensted
    Hedensted is a town and municipality in the Central Denmark Region known for its residential communities and local industry.
  • D. Blangsted
    Blangsted is a surname most notably associated with Folmar Blangsted, a film editor.
  • E. Egeskov
    Egeskov is a village on the island of Funen in Denmark best known for the nearby Renaissance water castle Egeskov Castle, one of Europe’s best-preserved moated castles.
  • 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_69e0b4ce39108190a6e8e5df4f1c8dc5 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2fc0cd081909e264cda686579ea completed April 21, 2026, 12:21 a.m.
Created at: April 16, 2026, 12:41 p.m.