Triple
T23194651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humen Opium Destruction |
E579840
|
entity |
| Predicate | confiscatedFrom |
P5949
|
FINISHED |
| Object | foreign merchants in Canton |
—
|
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: foreign merchants in Canton | Statement: [Humen Opium Destruction, confiscatedFrom, foreign merchants in Canton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confiscatedFrom Context triple: [Humen Opium Destruction, confiscatedFrom, foreign merchants in Canton]
-
A.
confiscatedBy
chosen
Indicates that something has been taken away and seized by an authority or agent, typically as a legal or disciplinary action.
-
B.
stolenFrom
Indicates that something was taken unlawfully from a particular source or owner.
-
C.
stolenBy
Indicates that something has been taken unlawfully or without permission by a particular entity.
-
D.
lootedBy
Indicates that something has been forcibly taken or plundered by a specified agent or group.
-
E.
confiscationContext
Indicates the circumstances, reasons, or legal basis under which something is seized or taken away from its owner by an authority.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fda64cc8190aeb5ccd8d8d20858 |
completed | April 29, 2026, 4:58 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:06 p.m.