Triple
T28338691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir Jafar |
E717751
|
entity |
| Predicate | reasonForInstallation |
P180503
|
FINISHED |
| Object | support to British at Battle of Plassey |
—
|
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: support to British at Battle of Plassey | Statement: [Mir Jafar, reasonForInstallation, support to British at Battle of Plassey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForInstallation Context triple: [Mir Jafar, reasonForInstallation, support to British at Battle of Plassey]
-
A.
reasonForNonInstallation
Indicates the explanation or cause for why an expected installation did not occur.
-
B.
reasonForDeployment
Indicates the underlying cause, purpose, or justification for which an entity is deployed or put into operation.
-
C.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
D.
intendedInstallation
Indicates that one entity is meant or planned to be installed in, on, or as part of another entity or environment.
-
E.
requiresInstallation
Indicates that one entity must be installed or set up before the other can be used or become operational.
- F. None of above. chosen
Provenance (4 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 28, 2026, 12:38 a.m.