Triple
T23573018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohaniya |
E580169
|
entity |
| Predicate | MLA2017Party |
P153221
|
FINISHED |
| Object | Bharatiya Janata Party |
—
|
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: Bharatiya Janata Party | Statement: [Rohaniya, MLA2017Party, Bharatiya Janata Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MLA2017Party Context triple: [Rohaniya, MLA2017Party, Bharatiya Janata Party]
-
A.
hadMLAParty
Indicates that an entity hosted or participated in a party or social gathering associated with the MLA (e.g., during an MLA conference or event).
-
B.
MPPartyAtElection2019
Indicates the political party with which an MP was affiliated at the time of the 2019 election.
-
C.
formerMLAParty
Indicates that an individual previously served as a Member of the Legislative Assembly (MLA) representing a particular political party, but no longer does so.
-
D.
ledByParty
Indicates that an organization, group, or governing body is under the leadership or control of a specified political party.
-
E.
hasRepresentativeParty
Indicates that an entity is officially represented or acted for by a particular political party or organized group.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd40c9c8190b666a2010d723bf1 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:37 p.m.