Triple

T7132673
Position Surface form Disambiguated ID Type / Status
Subject German Eighth Army E166227 entity
Predicate nativeName P15 FINISHED
Object 8. Armee E44980 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: 8. Armee | Statement: [German Eighth Army, nativeName, 8. Armee]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 8. Armee
Context triple: [German Eighth Army, nativeName, 8. Armee]
  • A. 10. Armee
    10. Armee was a field army of the German Wehrmacht that saw major combat on the Italian Front during World War II.
  • B. 17. Armee
    17. Armee was a field army of the German Wehrmacht that fought primarily on the Eastern Front during World War II.
  • C. 8th Army
    The 8th Army was a major British field army of the Second World War, best known for its pivotal role in the North African campaign, including the Battle of El Alamein.
  • D. 8th Army chosen
    The 8th Army was a major field formation of the German Wehrmacht that took part in early World War II campaigns, including the invasion of Poland.
  • E. 4th Army
    The 4th Army was a major field formation of the German Wehrmacht that took part in key early World War II campaigns, including the invasion of Poland.
  • 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_69c68884a9388190af42f90d1c1a7151 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e6703ad88190a498665500fee5a1 completed March 27, 2026, 8:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7a341ede88190b43f26f1dad7bf70 completed March 28, 2026, 9:45 a.m.
Created at: March 27, 2026, 2:45 p.m.