Triple

T12226278
Position Surface form Disambiguated ID Type / Status
Subject Schmalkaldic League E291358 entity
Predicate hasMember P10 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: [Schmalkaldic League, hasMember, City of Emden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: City of Emden
Context triple: [Schmalkaldic League, hasMember, 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. Heiligenhafen
    Heiligenhafen is a coastal town in northern Germany on the Baltic Sea, known for its fishing harbor, beaches, and tourism.
  • D. City of Zeeland
    The City of Zeeland is a small community in western Michigan known for its Dutch heritage, tight-knit neighborhoods, and role as part of the broader Holland–Zeeland urban region.
  • E. 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.
  • 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_69d6ab668acc8190963ba424049d6aee completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91ca2101c8190955c36704935036a completed April 10, 2026, 3:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69f60aa9023881909f8373e02d2cad4b completed May 2, 2026, 2:31 p.m.
Created at: April 8, 2026, 9:51 p.m.