Triple

T7198378
Position Surface form Disambiguated ID Type / Status
Subject Naval Base Frederikshavn E168673 entity
Predicate location P40 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: [Naval Base Frederikshavn, location, Frederikshavn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frederikshavn
Context triple: [Naval Base Frederikshavn, location, 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. 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.
  • C. Svendborg
    Svendborg is a historic coastal town and seaport in southern Denmark known for its maritime heritage and location on the island of Funen.
  • D. Fredericia
    Fredericia is a Danish coastal town in Jutland known for its historic 17th-century fortress and well-preserved ramparts.
  • E. Korsør
    Korsør is a Danish coastal town on the island of Zealand, known for its strategic position by the Great Belt strait and its historic maritime and military significance.
  • 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_69c68a5376748190bb500f03df86e93e completed March 27, 2026, 1:46 p.m.
NER Named-entity recognition batch_69c6e92a5d288190955f703470e75bf3 completed March 27, 2026, 8:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7fa67ec208190b513bf7e8252cdcb completed March 28, 2026, 3:57 p.m.
Created at: March 27, 2026, 2:52 p.m.