Triple
T13840321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New England merchants |
E332638
|
entity |
| Predicate | reasonForOppositionToWarOf1812 |
P111720
|
FINISHED |
| Object | disruption of Atlantic trade |
—
|
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: disruption of Atlantic trade | Statement: [New England merchants, reasonForOppositionToWarOf1812, disruption of Atlantic trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForOppositionToWarOf1812 Context triple: [New England merchants, reasonForOppositionToWarOf1812, disruption of Atlantic trade]
-
A.
positionOnWarOf1812
Indicates a stance, opinion, or alignment that an entity holds regarding the War of 1812.
-
B.
causeOfConflictWithBritish
Indicates that the subject is a source or reason for a conflict or dispute involving the British.
-
C.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
-
D.
annexationOpposedBy
Indicates that an annexation is met with opposition or resistance from a specified party or entity.
-
E.
reasonForBoycott
Indicates that one entity is the cause, motive, or justification for another entity’s decision to initiate or participate in a boycott.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02ae5e4c8190ad85ad2968bc71b2 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:13 p.m.