Triple
T35720844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | II Corps, Army of Virginia |
E1032465
|
entity |
| Predicate | subsequentAssignment |
P146596
|
FINISHED |
| Object | Army of the Potomac |
—
|
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: Army of the Potomac | Statement: [II Corps, Army of Virginia, subsequentAssignment, Army of the Potomac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentAssignment Context triple: [II Corps, Army of Virginia, subsequentAssignment, Army of the Potomac]
-
A.
laterAssignment
chosen
Indicates that one entity is assigned or allocated to another at a later time than some reference assignment or event.
-
B.
subsequentDesignation
Indicates that one designation or status follows and replaces another in a sequence or timeline.
-
C.
requiresAssignment
Indicates that one entity depends on another entity being assigned or allocated before it can proceed, function, or be considered valid.
-
D.
subsequentAuthority
Indicates that one authority or decision follows and is derived from, or dependent on, a prior authority or decision in a sequence.
-
E.
subsequentRole
Indicates that one role or position is held after, and in succession to, another role or position.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.