Triple

T9554007
Position Surface form Disambiguated ID Type / Status
Subject Northeastern Army E230494 entity
Predicate hasUnit P35 FINISHED
Object 2nd Division E806074 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: 2nd Division | Statement: [Northeastern Army, hasUnit, 2nd Division]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 2nd Division
Context triple: [Northeastern Army, hasUnit, 2nd Division]
  • A. 2nd Division chosen
    The 2nd Division is a major military formation within Japan’s Ground Self-Defense Force, responsible for regional defense and operational readiness under the Northern Army.
  • B. 3rd Division
    The 3rd Division is a renowned U.S. Army infantry division noted for its extensive combat history in major conflicts from World War I through the present.
  • C. 1st Division
    The 1st Division is a key formation of the Australian Army, historically notable for its role in major conflicts such as World War I and World War II.
  • D. 4th Division
    The 4th Division is a military formation that serves as one of the key combat units within Japan’s Western Army.
  • E. 5th Division
    The 5th Division was a long-serving infantry division of the British Army that saw extensive action in major conflicts including both World Wars.
  • 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_69ca847d3be8819099c9dad2a7e786f1 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd99217de48190b528e14fd02ee987 completed April 1, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69d190d741588190a2cced8da13036bb completed April 4, 2026, 10:29 p.m.
Created at: March 30, 2026, 8:02 p.m.