Triple
T26499193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of North Anna |
E669369
|
entity |
| Predicate | unionArmyCommander |
P26185
|
FINISHED |
| Object | George G. Meade |
—
|
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: George G. Meade | Statement: [Battle of North Anna, unionArmyCommander, George G. Meade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionArmyCommander Context triple: [Battle of North Anna, unionArmyCommander, George G. Meade]
-
A.
commandingUnionArmy
chosen
Indicates that one entity holds the role or responsibility of leading and directing the Union Army.
-
B.
primaryConfederateCommander
Indicates that one entity serves as the main commanding officer of Confederate forces for the other entity in a specific context or engagement.
-
C.
RepublicanCommander
Indicates that an individual serves as a military commander for the Republican side in a conflict.
-
D.
unionArmy
Indicates that an entity served in, was part of, or is otherwise affiliated with the Union Army (the United States Army of the North) during the American Civil War.
-
E.
appointedCommanderOfArmyOfThePotomacOn
Indicates that someone was officially appointed as commander of the Army of the Potomac on a specific date.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61358da60819085a4be177f30ac99 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:11 a.m.