Triple
T23767521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Helena |
E587424
|
entity |
| Predicate | confederateDepartment |
P145962
|
FINISHED |
| Object | Trans-Mississippi Department |
—
|
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: Trans-Mississippi Department | Statement: [Battle of Helena, confederateDepartment, Trans-Mississippi Department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confederateDepartment Context triple: [Battle of Helena, confederateDepartment, Trans-Mississippi Department]
-
A.
unionArmyDepartment
Indicates a relationship where an entity is associated with, assigned to, or operating under a specific department of the Union Army.
-
B.
militaryDepartment
chosen
Indicates that an entity functions as a military-related division, branch, or department within a larger organization or government structure.
-
C.
confederateArmyComponent
Indicates that one entity functions as a constituent unit, formation, or subpart of the Confederate army.
-
D.
formerDepartment
Indicates that one entity previously served as a department or subunit of another entity but no longer holds that status.
-
E.
confederateForcesType
Indicates the type or classification of confederate forces involved in a given military or conflict-related context.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c4638b248190b512841493778483 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:15 p.m.