Triple
T11312589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John R. Hodge |
E267876
|
entity |
| Predicate | notableCommand |
P2333
|
FINISHED |
| Object | XXIV Corps |
E533599
|
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: XXIV Corps | Statement: [John R. Hodge, notableCommand, XXIV Corps]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XXIV Corps Context triple: [John R. Hodge, notableCommand, XXIV Corps]
-
A.
XXIV Corps
chosen
XXIV Corps was a U.S. Army corps-level formation that saw major combat in the Pacific Theater during World War II, including the Battle of Okinawa.
-
B.
XIX Corps
XIX Corps was a U.S. Army corps-level formation that saw significant combat in the European Theater during World War II, particularly in the Normandy campaign and subsequent operations across France and Germany.
-
C.
XV Corps
XV Corps is a key field formation of the Indian Army responsible for military operations and security in the Kashmir region.
-
D.
XV Corps
XV Corps was a field corps of the Ottoman Army that served as a major combat formation during World War I.
-
E.
XXXIII Corps
XXXIII Corps is a field corps of the Indian Army responsible for operations in parts of India’s eastern and northeastern regions.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c1b7dc81908d8cc768c47390d3 |
completed | April 9, 2026, 6:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e50a7fc06881909afe85a600d25ff2 |
completed | April 19, 2026, 5:01 p.m. |
Created at: April 8, 2026, 9:32 p.m.