Triple

T20167547
Position Surface form Disambiguated ID Type / Status
Subject Duke of Anhalt E491864 entity
Predicate appliesToTerritory P647 FINISHED
Object Anhalt 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: Anhalt | Statement: [Duke of Anhalt, appliesToTerritory, Anhalt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anhalt
Context triple: [Duke of Anhalt, appliesToTerritory, Anhalt]
  • A. Anhalt chosen
    Anhalt is a historical region in central Germany that once formed a duchy and later a state, now largely part of the federal state of Saxony-Anhalt.
  • B. Sachse
    Sachse is a suburban city in the Dallas–Fort Worth metropolitan area of northeastern Texas.
  • C. Brannenburg
    Brannenburg is a Bavarian municipality in southern Germany, known for its scenic Alpine setting and outdoor recreation opportunities.
  • D. North Hesse
    North Hesse is a region in the northern part of the German state of Hesse, centered around the city of Kassel and known for its forests, hills, and cultural heritage.
  • E. Nordhoff
    Nordhoff is a surname most notably associated with American author and journalist Charles Nordhoff.
  • 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_69da6266c6888190bc1a3ecf24814d34 completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e66845cb588190820c50eea0c40d83 completed April 20, 2026, 5:54 p.m.
Created at: April 11, 2026, 11:35 p.m.