Triple
T2316547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charter Act 1833 |
E51077
|
entity |
| Predicate | terminated |
P2540
|
FINISHED |
| Object | East India Company trade monopoly in India |
—
|
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: East India Company trade monopoly in India | Statement: [Charter Act 1833, terminated, East India Company trade monopoly in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminated Context triple: [Charter Act 1833, terminated, East India Company trade monopoly in India]
-
A.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
B.
committed
Indicates that an agent has carried out or been responsible for a specific act, event, or wrongdoing.
-
C.
concluded
chosen
Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
-
D.
stoppedAt
Indicates that an entity has come to a halt or pause at a specific location or point in time.
-
E.
closedAsTerminal
Indicates that a process, case, or interaction has been concluded in a final, non-reopenable (terminal) state.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.