Triple

T13164324
Position Surface form Disambiguated ID Type / Status
Subject Prince-Bishopric of Lübeck E312806 entity
Predicate seatOfBishop P2276 FINISHED
Object Eutin E631963 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: Eutin | Statement: [Prince-Bishopric of Lübeck, seatOfBishop, Eutin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eutin
Context triple: [Prince-Bishopric of Lübeck, seatOfBishop, Eutin]
  • A. Eutin chosen
    Eutin is a historic town in northern Germany’s Schleswig-Holstein region, known for its picturesque lakeside setting, castle, and cultural festivals.
  • B. Halberstadt
    Halberstadt is a historic town in the German state of Saxony-Anhalt, known for its medieval architecture and role as a former episcopal seat.
  • C. Lankwitz
    Lankwitz is a residential locality in the southwestern part of Berlin, known for its quiet neighborhoods, green spaces, and mix of historic and modern architecture.
  • D. Lauenburg
    Lauenburg is a historic town in northern Germany situated on the banks of the Elbe River.
  • E. Magdeburg
    Magdeburg is a historic city in central Germany, known for its medieval cathedral, role as a major trading and industrial center, and location on the Elbe River.
  • 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_69d806ac3ee081909b2fd27d060aa974 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98c0bf5a48190bf245dceee24b579 completed April 10, 2026, 11:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbc311b1248190b9ceb2854e93171a completed May 6, 2026, 10:39 p.m.
Created at: April 9, 2026, 9:13 p.m.