Triple
T6263124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British opium trade in China |
E140347
|
entity |
| Predicate | legalStatusInChina |
P69795
|
FINISHED |
| Object | illegal |
—
|
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: illegal | Statement: [British opium trade in China, legalStatusInChina, illegal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInChina Context triple: [British opium trade in China, legalStatusInChina, illegal]
-
A.
legalStatusInTaiwan
Indicates the legal status or recognition that an entity has within the jurisdiction of Taiwan.
-
B.
ethnicStatusInChina
Indicates the ethnic classification or status that an entity holds within the sociopolitical context of China.
-
C.
legalStatusInManyCountries
Indicates that the subject has a particular legal classification or standing that is recognized across numerous countries.
-
D.
legalStatusInHomeland
Indicates the legal status or classification an entity holds within its country or place of origin.
-
E.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
- 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.