Triple
T37132535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mill Springs |
E919561
|
entity |
| Predicate | UnionArmyUnit |
P35239
|
FINISHED |
| Object | Army of the Ohio |
E133312
|
NE 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: Army of the Ohio | Statement: [Battle of Mill Springs, UnionArmyUnit, Army of the Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UnionArmyUnit Context triple: [Battle of Mill Springs, UnionArmyUnit, Army of the Ohio]
-
A.
unionArmy
chosen
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.
-
B.
unionArmyDepartment
Indicates a relationship where an entity is associated with, assigned to, or operating under a specific department of the Union Army.
-
C.
alliedRegiment
Indicates that one regiment is formally associated or cooperating as an ally with another regiment.
-
D.
notableMilitaryUnit
Indicates that an entity is a military unit that holds particular significance, prominence, or recognition in some context.
-
E.
armyUnion
Indicates that two or more military forces are joined together into a single unified army or coalition force.
- F. None of above.
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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3f6a23b06c81909e1067166f0c9c0f |
completed | June 27, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.