Triple
T1418124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir Jafar |
E31964
|
entity |
| Predicate | causeOfRiseToPower |
P4209
|
FINISHED |
| Object | British military support |
—
|
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: British military support | Statement: [Mir Jafar, causeOfRiseToPower, British military support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfRiseToPower Context triple: [Mir Jafar, causeOfRiseToPower, British military support]
-
A.
reasonForStartOfReign
Indicates the cause, circumstance, or event that led to the beginning of an entity’s reign.
-
B.
cameToPowerThrough
chosen
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
C.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
D.
cameToPowerIn
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
-
E.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c404e92c8190bd018673383f4534 |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.