Triple

T1033632
Position Surface form Disambiguated ID Type / Status
Subject 40th Army Corps E22308 entity
Predicate militaryBranch P253 FINISHED
Object Heer E9485 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: Heer | Statement: [40th Army Corps, militaryBranch, Heer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heer
Context triple: [40th Army Corps, militaryBranch, Heer]
  • A. Heer chosen
    The Heer was the land-based component of Nazi Germany’s armed forces, serving as its primary army during World War II.
  • B. Hein
    Hein is a Dutch surname most notably borne by Piet Hein, a renowned 17th-century naval officer and folk hero of the Dutch Republic.
  • C. König
    König is a German-language surname borne by numerous individuals, including notable figures in fields such as religion, science, and the arts.
  • D. Kœnig
    Kœnig is a French surname most notably associated with figures such as General Marie-Pierre Kœnig, a prominent military leader during World War II.
  • E. Sieg
    The Sieg is a river in western Germany that flows through North Rhine-Westphalia and Rhineland-Palatinate before joining the Rhine.
  • 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_69a493d848848190aed4011b34b2e8d3 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b812c9948190a37c2b1d3d32ea38 completed March 1, 2026, 10:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac3bc15a6c81909a71bf17b5cd4019 completed March 7, 2026, 2:52 p.m.
Created at: March 1, 2026, 7:41 p.m.