Triple
T18028510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Wauhatchie |
E431323
|
entity |
| Predicate | aimOfUnionForces |
P129514
|
FINISHED |
| Object | to secure and defend the Cracker Line |
—
|
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: to secure and defend the Cracker Line | Statement: [Battle of Wauhatchie, aimOfUnionForces, to secure and defend the Cracker Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfUnionForces Context triple: [Battle of Wauhatchie, aimOfUnionForces, to secure and defend the Cracker Line]
-
A.
aimOfAllies
Indicates that one entity represents the shared goal or objective pursued collectively by a group of allied entities.
-
B.
aimOfAlliance
Indicates that a specified goal, purpose, or objective is the intended focus or motivation of an alliance between entities.
-
C.
unionForces
Indicates that multiple forces are combined into a single, unified force acting together.
-
D.
aimedToUnify
Indicates an intention or effort by one entity to bring multiple entities, groups, or elements together into a single unified whole.
-
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. chosen
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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be332a7081909124abdd98430a8a |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:25 a.m.