Triple

T5404842
Position Surface form Disambiguated ID Type / Status
Subject Warburg family E120866 entity
Predicate associatedWithCity P1481 FINISHED
Object Hamburg E7419 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: Hamburg | Statement: [Warburg family, associatedWithCity, Hamburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hamburg
Context triple: [Warburg family, associatedWithCity, Hamburg]
  • A. Hamburg chosen
    Hamburg is Germany’s second-largest city and a major northern European port and cultural center on the River Elbe.
  • B. Bremen
    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.
  • C. 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.
  • D. Bremerhaven
    Bremerhaven is a major German port city on the North Sea, known for its maritime industry, shipbuilding, and role as a key hub for trade and logistics.
  • E. Cologne
    Cologne is a historic German city on the Rhine River, renowned for its Gothic cathedral, vibrant cultural scene, and status as a major economic and media hub.
  • 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_69bd46391c0c81909fa484446732b6a3 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd8775e964819085c0ff5afea35f0e completed March 20, 2026, 5:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69bfe14608d88190ba2573da7cb783fe completed March 22, 2026, 12:32 p.m.
Created at: March 20, 2026, 2:05 p.m.