Triple

T1144620
Position Surface form Disambiguated ID Type / Status
Subject Captain Frans Banning Cocq E23534 entity
Predicate birthPlace P1 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: [Captain Frans Banning Cocq, birthPlace, Bremen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bremen
Context triple: [Captain Frans Banning Cocq, birthPlace, 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_69a493ef399c8190b04b9146d2314f59 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4bc5008d8819095c1ffb5db5b4911 completed March 1, 2026, 10:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69aebee55ea4819097baa92110f35769 completed March 9, 2026, 12:36 p.m.
Created at: March 1, 2026, 7:44 p.m.