Triple

T17985841
Position Surface form Disambiguated ID Type / Status
Subject Battle of Paltzig E430229 entity
Predicate location P40 FINISHED
Object Neumark 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: Neumark | Statement: [Battle of Paltzig, location, Neumark]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neumark
Context triple: [Battle of Paltzig, location, Neumark]
  • A. Neumark
    Neumark is a small town in the Weimarer Land district of the German state of Thuringia.
  • B. Neumark region chosen
    The Neumark region was a historical borderland of Brandenburg-Prussia in eastern Germany, located east of the Oder River and long contested between German and Polish powers.
  • C. Neuhof
    Neuhof is a district (Ortsteil) of the town of Taunusstein in the Rheingau-Taunus-Kreis region of Hesse, Germany.
  • D. Neuhof
    Neuhof is a district in Strasbourg, France, that serves as a key hub in the city’s bus transportation network.
  • E. Kraichgau
    Kraichgau is a hilly, fertile region in southwestern Germany known for its agriculture, vineyards, and picturesque landscapes between the Black Forest and the Odenwald.
  • 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_69d8b90364248190a37381adea932f42 completed April 10, 2026, 8:46 a.m.
NER Named-entity recognition batch_69e4b29b4e808190af06074168169035 completed April 19, 2026, 10:46 a.m.
Created at: April 10, 2026, 10:23 a.m.