Triple
T21968511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Nashville |
E542520
|
entity |
| Predicate | UnionTactic |
P1716
|
FINISHED |
| Object | Two-day offensive against Confederate flanks |
—
|
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: Two-day offensive against Confederate flanks | Statement: [Battle of Nashville, UnionTactic, Two-day offensive against Confederate flanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UnionTactic Context triple: [Battle of Nashville, UnionTactic, Two-day offensive against Confederate flanks]
-
A.
unionForces
Indicates that multiple forces are combined into a single, unified force acting together.
-
B.
tactic
chosen
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
C.
unionForcesComposition
Indicates that multiple forces are combined or aggregated to form a single resultant force.
-
D.
unionSide
Indicates that an entity is aligned with, represents, or acts on behalf of a labor union in a labor-related relationship or context.
-
E.
UnionForcesType
Indicates that one entity is associated with, composed of, or characterized by a specific type or category of union forces.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1245d50d08190a4bf93139daa77eb |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8:02 p.m.