Triple

T16273839
Position Surface form Disambiguated ID Type / Status
Subject Mölndal E395071 entity
Predicate hasTwinTown P919 FINISHED
Object Frederikshavn E493638 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: Frederikshavn | Statement: [Mölndal, hasTwinTown, Frederikshavn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frederikshavn
Context triple: [Mölndal, hasTwinTown, Frederikshavn]
  • A. Frederikshavn chosen
    Frederikshavn is a port town in northern Jutland, Denmark, known for its ferry connections to Norway and Sweden and its maritime industry.
  • B. Vordingborg
    Vordingborg is a historic coastal town in southern Denmark known for the ruins of Vordingborg Castle and its prominent Goose Tower.
  • C. Faaborg
    Faaborg is a historic coastal town on the island of Funen in southern Denmark, known for its well-preserved old town, harbor, and cultural attractions.
  • D. Nykøbing Mors
    Nykøbing Mors is a Danish coastal town on the island of Mors, known as its main urban center and a local hub for fishing, trade, and tourism.
  • E. Svendborg
    Svendborg is a historic coastal town and seaport in southern Denmark known for its maritime heritage and location on the island of Funen.
  • 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_69d87f221d8081909b0b2063e7528ba2 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2460b22d88190bdc7cf509cf74198 completed April 17, 2026, 2:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a002da0a2908190923e61bdeb92567d completed May 10, 2026, 7:02 a.m.
Created at: April 10, 2026, 5:05 a.m.