Triple
T10711625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Savage’s Station |
E252550
|
entity |
| Predicate | UnionAction |
P95602
|
FINISHED |
| Object | retreat toward the James River |
—
|
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: retreat toward the James River | Statement: [Battle of Savage’s Station, UnionAction, retreat toward the James River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UnionAction Context triple: [Battle of Savage’s Station, UnionAction, retreat toward the James River]
-
A.
union
Indicates that two or more sets are combined into a single set containing all elements that belong to at least one of them.
-
B.
UnionStrength
Indicates the degree of solidarity, cohesion, and collective bargaining power within or among unions in a given context.
-
C.
unionForces
Indicates that multiple forces are combined into a single, unified force acting together.
-
D.
unionRepresents
Indicates that one entity serves as the official representative or acting body on behalf of a union in relation to another entity or context.
-
E.
unionInvolved
Indicates that a labor union is involved in, associated with, or plays a role in the specified action, event, or relationship between entities.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fe523de08190a82c8f057fe8baf6 |
completed | April 9, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:13 p.m.