Triple
T23539598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anil Yashwant Tipnis |
E577701
|
entity |
| Predicate | playedKeyLeadershipRoleIn |
P3512
|
FINISHED |
| Object | Kargil War |
—
|
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: Kargil War | Statement: [Anil Yashwant Tipnis, playedKeyLeadershipRoleIn, Kargil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedKeyLeadershipRoleIn Context triple: [Anil Yashwant Tipnis, playedKeyLeadershipRoleIn, Kargil War]
-
A.
playedKeyRoleIn
chosen
Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
-
B.
playedEarlyRoleIn
Indicates that one entity contributed significantly to the initial or formative stages of another entity’s development, success, or emergence.
-
C.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
D.
replacesInLeadRole
Indicates that one entity takes over or substitutes for another entity in the primary or leading role within a given context or production.
-
E.
hasPlayedRole
Indicates that an entity has performed or portrayed a particular role or character in some context (such as a film, play, or production).
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1a66b88190811b38523ea606fe |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.