Triple
T5989643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army of the Ohio |
E133312
|
entity |
| Predicate | notableBattlefieldRole |
P28183
|
FINISHED |
| Object | reinforced Union forces at the Battle of Shiloh |
—
|
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: reinforced Union forces at the Battle of Shiloh | Statement: [Army of the Ohio, notableBattlefieldRole, reinforced Union forces at the Battle of Shiloh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBattlefieldRole Context triple: [Army of the Ohio, notableBattlefieldRole, reinforced Union forces at the Battle of Shiloh]
-
A.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
B.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
notableCommanderSide
Indicates that a particular military or strategic side is notably commanded or led by a specified commander.
-
D.
battleOutcomeRole
Indicates the specific role an entity played in a battle with respect to its outcome (e.g., victor, loser, ally, defender).
-
E.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc76fd481908cc3f327e532a1a6 |
completed | March 22, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c049de98648190962b14fd341c93da |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.