Triple

T23497399
Position Surface form Disambiguated ID Type / Status
Subject Robert Koldewey E571738 entity
Predicate familyName P18 FINISHED
Object Koldewey 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: Koldewey | Statement: [Robert Koldewey, familyName, Koldewey]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koldewey
Context triple: [Robert Koldewey, familyName, Koldewey]
  • A. Koldewey chosen
    Koldewey is a German surname most notably associated with Robert Koldewey, the archaeologist who led the excavation of ancient Babylon.
  • B. Weigert
    Weigert is a German-language surname borne by various notable individuals in fields such as science, sports, and the arts.
  • C. Kniphausen
    Kniphausen is a historical territory in present-day Germany that once functioned as a small semi-independent lordship under various regional powers.
  • D. Beckstein
    Beckstein is a wine-producing village and district of the town Lauda-Königshofen in the Main-Tauber region of Baden-Württemberg, Germany.
  • E. Lehwaldt
    Lehwaldt was a Prussian field marshal best known for commanding Prussian forces in the early campaigns of the Seven Years' War in Europe.
  • 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_69e245b4829881909b77a70e942bbd54 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a7e0c5a48190badb8303f40f6180 completed April 29, 2026, 6:40 a.m.
Created at: April 17, 2026, 6:05 p.m.