Triple

T10302018
Position Surface form Disambiguated ID Type / Status
Subject 2nd Far Eastern Front E241653 entity
Predicate includedUnit P1393 FINISHED
Object 15th Army E819093 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: 15th Army | Statement: [2nd Far Eastern Front, includedUnit, 15th Army]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 15th Army
Context triple: [2nd Far Eastern Front, includedUnit, 15th Army]
  • A. 15th Army
    The 15th Army was a German field army of the Wehrmacht that operated primarily on the Western Front during World War II.
  • B. 15th Army chosen
    The 15th Army was a field army of the Imperial Japanese Army that operated primarily in Southeast Asia during World War II.
  • C. 25th Army
    The 25th Army was a Japanese Imperial Army formation active during World War II, notably involved in the invasion and occupation of Southeast Asian territories.
  • D. 25th Army
    The 25th Army was a late-World War II German field army that primarily conducted defensive operations in the western Netherlands under the Wehrmacht.
  • E. 19th Army
    The 19th Army was a field army of the Soviet Red Army that fought on the Eastern Front during World War II, notably in the early defensive battles against the German invasion.
  • 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_69d381aaafc08190af475ef58dc16aba completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d30716d8819085e25a78e6af3b9d completed April 7, 2026, 9:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69d7fb4f840c81909beaf910c1ac3751 completed April 9, 2026, 7:17 p.m.
Created at: April 6, 2026, 11:45 a.m.