Triple
T13840320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New England merchants |
E332638
|
entity |
| Predicate | reactionToWarOf1812 |
P98821
|
FINISHED |
| Object | largely opposed |
—
|
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: largely opposed | Statement: [New England merchants, reactionToWarOf1812, largely opposed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactionToWarOf1812 Context triple: [New England merchants, reactionToWarOf1812, largely opposed]
-
A.
positionOnWarOf1812
chosen
Indicates a stance, opinion, or alignment that an entity holds regarding the War of 1812.
-
B.
onlyRevolutionaryWarBattleEntirelyOn
Indicates that the referenced battle is the sole Revolutionary War engagement fought entirely within the specified location or context.
-
C.
statusDuringWar
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
D.
stateDuringWar
Indicates that a state or condition exists specifically in the context of, or for the duration of, a war or armed conflict.
-
E.
statusBeforeWar
Indicates the condition or situation of an entity as it existed prior to the onset of a specified war.
- 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_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. |
Created at: April 9, 2026, 10:13 p.m.