Triple
T26199303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assam Accord |
E655188
|
entity |
| Predicate | signatoryRoleOfRajivGandhi |
P52735
|
FINISHED |
| Object | Prime Minister of 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: Prime Minister of India | Statement: [Assam Accord, signatoryRoleOfRajivGandhi, Prime Minister of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatoryRoleOfRajivGandhi Context triple: [Assam Accord, signatoryRoleOfRajivGandhi, Prime Minister of India]
-
A.
signatoryMinister
Indicates that a minister has formally signed or endorsed a document, agreement, or treaty as an official signatory.
-
B.
signatureRole
Indicates the specific function or capacity in which an entity participates in a signing or signature-related action.
-
C.
signatoryHeadOfGovernment
chosen
Indicates that the person serving as head of government is an official signer or ratifier of a specified agreement, treaty, or document.
-
D.
signatoryDiplomat
Indicates that a diplomat is an official signatory to an agreement, treaty, or formal document.
-
E.
foundingSignatory
Indicates that an entity was an original signer or member at the founding of another entity, agreement, or organization.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cd9e50481908d1559e6ec048bc1 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:47 p.m.