Triple
T22554921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Champaubert |
E557654
|
entity |
| Predicate | campaignOpponent |
P148634
|
FINISHED |
| Object | Coalition armies invading France in 1814 |
—
|
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: Coalition armies invading France in 1814 | Statement: [Battle of Champaubert, campaignOpponent, Coalition armies invading France in 1814]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignOpponent Context triple: [Battle of Champaubert, campaignOpponent, Coalition armies invading France in 1814]
-
A.
campaignOpponents
Indicates that two entities are on opposing sides in a political or advocacy campaign.
-
B.
electionOpponent
Indicates that two individuals are rivals competing against each other in the same election.
-
C.
opponentCampaign
Indicates a relationship where one campaign is positioned as competing against or opposing another campaign.
-
D.
opponentCandidate
Indicates that one entity is a rival or competing candidate against another in the same contest or election.
-
E.
mainOpposingPolitician
Indicates that one politician is the primary political rival or adversary of another.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f78d8288190871d54db0a7f454b |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:52 p.m.