Triple

T1985983
Position Surface form Disambiguated ID Type / Status
Subject Hanseatic League E43142 entity
Predicate hasMember P10 FINISHED
Object Bremen E76455 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: Bremen | Statement: [Hanseatic League, hasMember, Bremen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bremen
Context triple: [Hanseatic League, hasMember, Bremen]
  • A. Bremen chosen
    Bremen is a city-state in northwestern Germany comprising the cities of Bremen and Bremerhaven, known for its historic Hanseatic heritage and major port on the Weser River.
  • B. Braunschweig
    Braunschweig is a historic city in northern Germany known for its medieval architecture, cultural institutions, and role as an important economic and scientific center.
  • C. Hamburg
    Hamburg is Germany’s second-largest city and a major northern European port and cultural center on the River Elbe.
  • D. Lüneburg
    Lüneburg is a historic Hanseatic town in northern Germany renowned for its medieval architecture and former wealth from salt mining.
  • E. Lübeck
    Lübeck is a historic Hanseatic city in northern Germany renowned for its medieval architecture and long-standing role as a key trading hub on the Baltic Sea.
  • 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_69a88713ddc88190a969715658ebe7a8 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb8232d788190938f261fd4b2f2fd completed March 7, 2026, 5:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69b3bb56c2e081909168c0fef26bff44 completed March 13, 2026, 7:23 a.m.
Created at: March 4, 2026, 7:37 p.m.