Triple
T25371222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bowring Treaty |
E632935
|
entity |
| Predicate | imposedPolicyChange |
P9550
|
FINISHED |
| Object | reduction of import duties |
—
|
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: reduction of import duties | Statement: [Bowring Treaty, imposedPolicyChange, reduction of import duties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imposedPolicyChange Context triple: [Bowring Treaty, imposedPolicyChange, reduction of import duties]
-
A.
changePolicy
chosen
Indicates that an entity modifies, replaces, or updates an existing policy governing rules, procedures, or behaviors.
-
B.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
-
C.
hasPolicyChange
Indicates that a change has been made to an existing policy or set of policies affecting the related entities.
-
D.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
E.
sawPolicyChange
Indicates that an entity observed, experienced, or became aware of a change in policy affecting it or its context.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a11323e08190a8ec4687f8fefe7f |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:38 p.m.