Triple
T3994138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walton H. Walker |
E87059
|
entity |
| Predicate | commanded |
P2333
|
FINISHED |
| Object | I Corps |
E57355
|
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: I Corps | Statement: [Walton H. Walker, commanded, I Corps]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: I Corps Context triple: [Walton H. Walker, commanded, I Corps]
-
A.
I Corps
chosen
I Corps is a major U.S. Army corps-level headquarters responsible for commanding and coordinating large-scale land operations, with a primary focus on the Indo-Pacific region.
-
B.
I Corps
I Corps was a major British Army field formation that played key roles in both World Wars, particularly in early operations in France and Belgium.
-
C.
II Army Corps
II Army Corps was a major Italian military formation that served as a key combat unit of the Royal Italian Army, including on the Eastern Front during World War II.
-
D.
IV Corps
IV Corps was a British Army corps-level formation that played a significant role on the Western Front during World War I.
-
E.
VI Corps
VI Corps was a major field corps of the United States Army that commanded multiple divisions in key campaigns, particularly during World War II.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa1d9d8c8190982d092a73d38564 |
completed | March 9, 2026, 4:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5768c29f08190baa35f395ebee6bb |
completed | March 14, 2026, 2:54 p.m. |
Created at: March 9, 2026, 3:33 p.m.