Triple
T2516551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deputy Chairman of Rajya Sabha |
E55424
|
entity |
| Predicate | firstHolderAssumedOffice |
P38523
|
FINISHED |
| Object | 1952 |
—
|
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: 1952 | Statement: [Deputy Chairman of Rajya Sabha, firstHolderAssumedOffice, 1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHolderAssumedOffice Context triple: [Deputy Chairman of Rajya Sabha, firstHolderAssumedOffice, 1952]
-
A.
firstOfficeHolderStart
chosen
Indicates the date or time when the first person to hold a particular office or position began their term.
-
B.
officeHolderBecame
Indicates that an individual assumed or transitioned into holding a particular office or official position.
-
C.
firstInOfficeTo
Indicates that one entity was the earliest or first to hold a particular office or position in relation to another entity or context.
-
D.
firstOfficeHolder
Indicates that the subject is the very first individual to hold a particular office or position associated with the object.
-
E.
inauguralHolder
Indicates that the subject is the first person or entity to hold a particular position, title, office, or role.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0bf37c0819088d28b5081ba7556 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.