Triple
T20419853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nitish Kumar |
E500816
|
entity |
| Predicate | positionHeldInParliament |
P71555
|
FINISHED |
| Object | Member of Lok Sabha |
—
|
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: Member of Lok Sabha | Statement: [Nitish Kumar, positionHeldInParliament, Member of Lok Sabha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionHeldInParliament Context triple: [Nitish Kumar, positionHeldInParliament, Member of Lok Sabha]
-
A.
servedInParliamentFor
Indicates that a person held a parliamentary seat as a representative of a specified constituency, region, or jurisdiction.
-
B.
rankInParliament
Indicates the hierarchical position or level of authority that an individual holds within a parliamentary body.
-
C.
servedInParliament
chosen
Indicates that a person has held a position as a member of a parliamentary body during some period of time.
-
D.
positionHeldInLegislature
Indicates that an entity holds or has held a specific official role or seat within a legislative body.
-
E.
representedInParliamentSince
Indicates that an entity has held representation in a parliament continuously from a specified starting time.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67ba39f7081909358f1103a0f241c |
completed | April 20, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.