Triple
T22076005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dilip Kumar |
E545521
|
entity |
| Predicate | politicalOfficeTerm |
P17403
|
FINISHED |
| Object | Rajya Sabha member 2000–2006 |
—
|
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: Rajya Sabha member 2000–2006 | Statement: [Dilip Kumar, politicalOfficeTerm, Rajya Sabha member 2000–2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalOfficeTerm Context triple: [Dilip Kumar, politicalOfficeTerm, Rajya Sabha member 2000–2006]
-
A.
topPoliticalOffice
Indicates that the subject holds or is associated with the highest-ranking political office within a given governmental or political system.
-
B.
electedOffice
Indicates that an entity holds or has held a particular office or position as a result of an election.
-
C.
stateOfPoliticalOffice
Indicates the political office or governmental position currently held or associated with an entity.
-
D.
termInOffice
chosen
Indicates the period during which an individual officially holds a particular office or position.
-
E.
isPoliticalOffice
Indicates that the subject is a formal governmental or political position held within a public institution or authority.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b2bf60819082d38e671f160b0f |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.