Triple

T6945186
Position Surface form Disambiguated ID Type / Status
Subject Borssum E160778 entity
Predicate hasMunicipalAuthority P3379 FINISHED
Object City of Emden E605282 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: City of Emden | Statement: [Borssum, hasMunicipalAuthority, City of Emden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: City of Emden
Context triple: [Borssum, hasMunicipalAuthority, City of Emden]
  • A. city of Emden chosen
    The city of Emden is a historic seaport and independent city in northwestern Germany, located in East Frisia on the North Sea coast.
  • B. Emden
    Emden is a historic port city in northwestern Germany known for its maritime industry and location near the North Sea.
  • C. Emder Hafen
    Emder Hafen is the historic seaport of the city of Emden in northwestern Germany, serving as an important maritime and commercial hub on the North Sea coast.
  • D. Wilhelminaoord
    Wilhelminaoord is a village in the Dutch province of Drenthe, known for its origins as a 19th-century welfare colony and its inclusion in the UNESCO-listed Colonies of Benevolence.
  • E. Friedeburg
    Friedeburg is a small municipality in Lower Saxony, Germany, known for its rural character and location within the East Frisian region.
  • 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_69c68850419081909fb426b8f5a304c7 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6da8a65c48190b6862fc60f6c7f7a completed March 27, 2026, 7:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7ad6c3414819085b816c9455cee7a completed March 28, 2026, 10:29 a.m.
Created at: March 27, 2026, 2:28 p.m.