Triple
T964869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal African Company |
E20815
|
entity |
| Predicate | monopolyEnded |
P10839
|
FINISHED |
| Object | 1698 |
—
|
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: 1698 | Statement: [Royal African Company, monopolyEnded, 1698]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monopolyEnded Context triple: [Royal African Company, monopolyEnded, 1698]
-
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.
monopolyRestricted
Indicates that an entity’s monopoly power or exclusive control over a market, resource, or service is limited, regulated, or otherwise constrained.
-
C.
monopolyEndYear
chosen
Indicates the year in which a monopoly or exclusive control over a market, resource, or right comes to an end.
-
D.
monopolyStartYear
Indicates the year in which an entity first obtained or began exercising monopoly control in a particular market or domain.
-
E.
monopolyEndYearOnChinaTrade
Indicates the year in which an entity’s monopoly on trade with China came 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b431d61481908b53490e99670363 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a42c1481908d940cbe0aefdd3b |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.