Triple
T29215149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mansfield |
E740647
|
entity |
| Predicate | campaignObjectiveOpposed |
P80743
|
FINISHED |
| Object | Union Red River Campaign |
—
|
NE NERFINISHED |
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: Union Red River Campaign | Statement: [Battle of Mansfield, campaignObjectiveOpposed, Union Red River Campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignObjectiveOpposed Context triple: [Battle of Mansfield, campaignObjectiveOpposed, Union Red River Campaign]
-
A.
opposedProject
Indicates that an entity actively resisted, disagreed with, or worked against a particular project.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
oppositionTargeted
Indicates that an action or strategy is specifically directed against or aimed at an opposing party, group, or viewpoint.
-
D.
opponentCampaign
chosen
Indicates a relationship where one campaign is positioned as competing against or opposing another campaign.
-
E.
campaignObjectiveContext
Indicates the specific situational or strategic context in which a campaign’s objective is defined or pursued.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 12:13 p.m.