Triple
T392916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British East India Company |
E8918
|
entity |
| Predicate | monopolyEndYearOnChinaTrade |
P10840
|
FINISHED |
| Object | 1833 |
—
|
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: 1833 | Statement: [British East India Company, monopolyEndYearOnChinaTrade, 1833]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monopolyEndYearOnChinaTrade Context triple: [British East India Company, monopolyEndYearOnChinaTrade, 1833]
-
A.
monopolyOn
Indicates that one entity has exclusive control or rights over a resource, market, or activity, preventing others from participating on equal terms.
-
B.
confiscationYear
Indicates the year in which something was officially taken away or seized, typically by an authority.
-
C.
historicalPeriodOfProsperity
Indicates a time span in which a society, region, or entity experienced notable economic growth, stability, and overall flourishing.
-
D.
openedPortToForeignTrade
Indicates that an entity has allowed or enabled a port to conduct commercial trade with foreign countries.
-
E.
conquestYear
Indicates the year in which one entity successfully conquered or took control over another entity.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec7637c08190b695ec640edbf6c2 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96a8ca48190abbd8de9b02c115c |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea2dc3088190a2aeb4496aff3582 |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.