Triple
T29626185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horatio G. Wright |
E755147
|
entity |
| Predicate | hasPartInHisMilitaryCommand |
P194985
|
FINISHED |
| Object | infantry units of VI Corps |
—
|
LITERAL 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: infantry units of VI Corps | Statement: [Horatio G. Wright, hasPartInHisMilitaryCommand, infantry units of VI Corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartInHisMilitaryCommand Context triple: [Horatio G. Wright, hasPartInHisMilitaryCommand, infantry units of VI Corps]
-
A.
isMilitaryCommand
Indicates that one entity holds formal military authority or command over another entity or group.
-
B.
hadMilitaryFollowing
Indicates that an entity was supported or backed by a group of military personnel or forces.
-
C.
corpsCommandedUnder
Indicates that one military corps was commanded under the authority or control of another specified commander or higher-level unit.
-
D.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
E.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
- F. None of above. chosen
Provenance (4 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: April 28, 2026, 6:37 p.m.