Triple
T9383882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph Hooker |
E225855
|
entity |
| Predicate | relinquishedCommandOfArmyOfThePotomacOn |
P88633
|
FINISHED |
| Object | 1863-06-28 |
—
|
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: 1863-06-28 | Statement: [Joseph Hooker, relinquishedCommandOfArmyOfThePotomacOn, 1863-06-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relinquishedCommandOfArmyOfThePotomacOn Context triple: [Joseph Hooker, relinquishedCommandOfArmyOfThePotomacOn, 1863-06-28]
-
A.
commandingUnionArmy
Indicates that one entity holds the role or responsibility of leading and directing the Union Army.
-
B.
commanderAtGettysburg
Indicates that the subject served as a military commander at the Battle of Gettysburg.
-
C.
surrenderedCommander
Indicates that one commander formally yielded authority or control to another, typically as part of a surrender.
-
D.
armyCommanderAtGettysburg
Indicates that the person served as an army commander during the Battle of Gettysburg.
-
E.
commandingConfederateForces
Indicates that one entity holds the role or responsibility of directing and leading the military operations of the Confederate forces in relation to another entity.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50c23e7881908112597a1771afa5 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:44 p.m.