Triple

T20686368
Position Surface form Disambiguated ID Type / Status
Subject Leipzig lowlands E508428 entity
Predicate near P350 FINISHED
Object Saxony NE NERFINISHED

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: Saxony | Statement: [Leipzig lowlands, near, Saxony]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saxony
Context triple: [Leipzig lowlands, near, Saxony]
  • A. Saxony chosen
    Saxony is a historic region and former kingdom in eastern Germany, known for its cultural centers like Dresden and Leipzig and its significant role in Central European history.
  • B. Saxonia
    Saxonia is a line of high-end mechanical wristwatches by German luxury watchmaker A. Lange & Söhne, known for its minimalist design and precise craftsmanship.
  • C. Thuringia
    Thuringia is a federal state in central Germany known for its forested landscapes, historic cities like Weimar and Erfurt, and its rich cultural and intellectual heritage.
  • D. Brandenburg
    Brandenburg is a federal state in northeastern Germany that surrounds Berlin and is known for its lakes, forests, and historic Prussian heritage.
  • E. Brandenburg
    Brandenburg is a small city in Meade County, Kentucky, situated along the Ohio River and serving as the county seat.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4c1ed408190b72dd26b1e33f8a1 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6beacc30081908e57cd7f2c3ef047 completed April 21, 2026, 12:02 a.m.
Created at: April 16, 2026, 11:45 a.m.