Triple
T6263126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British opium trade in China |
E140347
|
entity |
| Predicate | tradeMechanism |
P69796
|
FINISHED |
| Object | smuggling |
—
|
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: smuggling | Statement: [British opium trade in China, tradeMechanism, smuggling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeMechanism Context triple: [British opium trade in China, tradeMechanism, smuggling]
-
A.
tradeSystem
Indicates a system or framework through which goods, services, or assets are exchanged between parties under defined rules or mechanisms.
-
B.
tradeNetwork
Indicates a relationship where entities are connected through the exchange of goods, services, or resources within an ongoing system of trade.
-
C.
negotiationMechanism
Indicates a process or method through which parties communicate and bargain to reach a mutually acceptable agreement.
-
D.
tradeMedium
Indicates that one entity serves as the medium or instrument through which another entity conducts trade or exchange transactions.
-
E.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
- 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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06387fec0819095b47a37b9402aa9 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05707d5408190a1d0fd80414ad957 |
completed | March 22, 2026, 8:54 p.m. |
Created at: March 22, 2026, 4:25 p.m.