Triple
T5105644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janata Dal (United) |
E115084
|
entity |
| Predicate | hasProminentLeaderFromState |
P61157
|
FINISHED |
| Object | Nitish Kumar from Bihar |
—
|
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: Nitish Kumar from Bihar | Statement: [Janata Dal (United), hasProminentLeaderFromState, Nitish Kumar from Bihar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentLeaderFromState Context triple: [Janata Dal (United), hasProminentLeaderFromState, Nitish Kumar from Bihar]
-
A.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
B.
hasMajorityLeader
Indicates that one entity serves as the primary or leading decision-making authority (majority leader) for another entity, typically within a governing or organizational body.
-
C.
hasFormerLeader
Indicates that an entity previously held the role of leader of another entity but no longer does.
-
D.
promotedLeader
Indicates that one entity has elevated another entity to a higher leadership position or role.
-
E.
hasDeputeLeader
Indicates that an entity serves as the deputy leader (second-in-command) of another entity.
- 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_69bd4440b3348190be1251fd8b7951f1 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75a7c6748190b02b7c2b617c830f |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd738ac2e0819099c06cdcc5e21d28 |
completed | March 20, 2026, 4:19 p.m. |
Created at: March 20, 2026, 1:41 p.m.