Triple

T37043026
Position Surface form Disambiguated ID Type / Status
Subject 359th Infantry Regiment E916831 entity
Predicate higherCommandWWII P47253 FINISHED
Object Third United States Army NE NERFINISHED

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: Third United States Army | Statement: [359th Infantry Regiment, higherCommandWWII, Third United States Army]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: higherCommandWWII
Context triple: [359th Infantry Regiment, higherCommandWWII, Third United States Army]
  • A. higherCommandDuringWWII chosen
    Indicates that one entity served as the superior military authority or command over another entity during World War II.
  • B. WWIITheater
    Indicates the geographic or operational theater in which a World War II-related event, action, or entity was involved.
  • C. commanderDuringWorldWarII
    Indicates that one entity served as a commander of the other specifically during the period of World War II.
  • D. sideInWorldWarII
    Indicates that an entity was aligned with or participated on a particular side during World War II.
  • E. worldWar
    Indicates a large-scale armed conflict involving multiple nations across different regions of the world, typically encompassing numerous battles, alliances, and theaters of war.
  • F. None of above.

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_69f76e93ec4c8190be81cf87354d9155 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fd9ff026a48190bfec33deeb3b2c43 completed May 8, 2026, 8:33 a.m.
PD Predicate disambiguation batch_69fd97d805bc8190ba12f429d3ad04c7 completed May 8, 2026, 7:59 a.m.
Created at: May 3, 2026, 4:14 p.m.