Triple
T2194534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIC |
E49939
|
entity |
| Predicate | teaMonopolyEnded |
P10839
|
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: [EIC, teaMonopolyEnded, 1833]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teaMonopolyEnded Context triple: [EIC, teaMonopolyEnded, 1833]
-
A.
monopolyEndedBy
Indicates that a previously existing monopoly was terminated or disrupted by a particular agent, event, or intervention.
-
B.
monopolyOn
Indicates that one entity has exclusive control or rights over a resource, market, or activity, preventing others from participating on equal terms.
-
C.
monopolyRestricted
Indicates that an entity’s monopoly power or exclusive control over a market, resource, or service is limited, regulated, or otherwise constrained.
-
D.
monopolyConfirmedBy
Indicates that the existence or status of a monopoly is validated or officially recognized by a specified confirming party or source.
-
E.
monopolyEndYear
chosen
Indicates the year in which a monopoly or exclusive control over a market, resource, or right comes to an end.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.