Triple

T2144660
Position Surface form Disambiguated ID Type / Status
Subject Imperial German Navy E47035 entity
Predicate mainBase P2909 FINISHED
Object Wilhelmshaven E41561 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: Wilhelmshaven | Statement: [Imperial German Navy, mainBase, Wilhelmshaven]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wilhelmshaven
Context triple: [Imperial German Navy, mainBase, Wilhelmshaven]
  • A. Wilhelmshaven chosen
    Wilhelmshaven is a coastal city in northwestern Germany known for its major naval base and port on the North Sea.
  • B. Dover
    Dover is a small town in eastern Dutchess County, New York, known for its rural character and location near the Connecticut border.
  • C. Dover
    Dover is one of the oldest permanent European settlements in what is now the U.S. state of New Hampshire, historically significant as an early colonial town and port.
  • D. Dover
    Dover is a coastal town in southeast England best known for its white chalk cliffs and its strategic port facing the narrowest part of the English Channel.
  • E. Harwich
    Harwich is a historic port town in Essex, England, which once served as a parliamentary borough represented in the British House of Commons.
  • 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_69a88a1933e0819094f18426ed74180f completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abbe223f848190a60bd0f15aed1021 completed March 7, 2026, 5:56 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae51b8152c81908c66d389bf14dc7e completed March 9, 2026, 4:51 a.m.
Created at: March 4, 2026, 7:44 p.m.