Triple
T30738784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vellore Mutiny |
E782635
|
entity |
| Predicate | authorityOpposed |
P437
|
FINISHED |
| Object | British East India Company |
—
|
NE NERFINISHED |
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: British East India Company | Statement: [Vellore Mutiny, authorityOpposed, British East India Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorityOpposed Context triple: [Vellore Mutiny, authorityOpposed, British East India Company]
-
A.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
opposedBecause
Indicates that one entity is opposed to another specifically due to a particular reason, cause, or justification.
-
C.
canOppose
Indicates that one entity has the ability or capacity to resist, counteract, or act in opposition to another entity or its actions.
-
D.
hasOpposedAuthority
Indicates that one entity holds authority that is in conflict with, challenges, or stands in opposition to the authority of another entity.
-
E.
opposedDuring
Indicates that one entity actively resisted or was in conflict with another entity during a specified time period or event.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 29, 2026, 8:37 p.m.