Triple

T13120623
Position Surface form Disambiguated ID Type / Status
Subject 17. Armee E311708 entity
Predicate hasNameInGerman P22792 FINISHED
Object 17. Armee E311708 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: 17. Armee | Statement: [17. Armee, hasNameInGerman, 17. Armee]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 17. Armee
Context triple: [17. Armee, hasNameInGerman, 17. Armee]
  • A. 17. Armee chosen
    17. Armee was a field army of the German Wehrmacht that fought primarily on the Eastern Front during World War II.
  • B. 10. Armee
    10. Armee was a field army of the German Wehrmacht that saw major combat on the Italian Front during World War II.
  • C. 7th Army
    The 7th Army was a major field army of the German Wehrmacht in World War II, active on the Western Front in campaigns including the defense of Normandy and the later stages of the war.
  • D. 7th Army
    The 7th Army was a field army of the Soviet Red Army that saw significant combat on the Eastern Front during World War II.
  • E. German 18th Army
    The German 18th Army was a Wehrmacht field army that operated primarily on the Eastern Front during World War II, participating in major operations in the northern sector against the Soviet Union.
  • 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_69d806a9fe888190b081e2d9ea665d6c completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98196e69081909111407ee3d9f08e completed April 10, 2026, 11:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6e286de608190bf46af2eb656bb79 completed May 3, 2026, 5:52 a.m.
Created at: April 9, 2026, 9:06 p.m.