Triple

T447546
Position Surface form Disambiguated ID Type / Status
Subject Duchy of Brunswick-Lüneburg E7054 entity
Predicate namedAfter P63 FINISHED
Object Lüneburg E74643 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: Lüneburg | Statement: [Duchy of Brunswick-Lüneburg, namedAfter, Lüneburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lüneburg
Context triple: [Duchy of Brunswick-Lüneburg, namedAfter, Lüneburg]
  • A. Lüneburg chosen
    Lüneburg is a historic Hanseatic town in northern Germany renowned for its medieval architecture and former wealth from salt mining.
  • B. Delmenhorst
    Delmenhorst is a mid-sized industrial and commuter city in northwestern Germany, located near Bremen in the federal state of Lower Saxony.
  • C. 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.
  • D. Hildesheim
    Hildesheim is a historic city in northern Germany renowned for its medieval architecture and UNESCO-listed Romanesque churches.
  • E. Wolfenbüttel
    Wolfenbüttel is a historic town in Lower Saxony, Germany, known for its Renaissance castle and rich cultural heritage.
  • 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_69a2e7e4676c81909ea0dbdecac0687c completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ef6429e881908aa758da64299a16 completed Feb. 28, 2026, 1:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad5897c8488190b5266a04150f81de completed March 8, 2026, 11:08 a.m.
Created at: Feb. 28, 2026, 1:12 p.m.