Triple
T31903327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LeT |
E814479
|
entity |
| Predicate | operationalCommander |
P1061
|
FINISHED |
| Object | Zaki-ur-Rehman Lakhvi |
—
|
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: Zaki-ur-Rehman Lakhvi | Statement: [LeT, operationalCommander, Zaki-ur-Rehman Lakhvi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalCommander Context triple: [LeT, operationalCommander, Zaki-ur-Rehman Lakhvi]
-
A.
jointOperationsCommander
Indicates that one entity serves as the commander responsible for overseeing joint operations involving multiple forces or organizations in relation to another entity.
-
B.
commander
chosen
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
C.
operationalCommand
Indicates that one entity issues or holds authoritative control over the actions or operations of another entity.
-
D.
operationalCommanderAttacker
Indicates that the subject serves as the operational commander directing and controlling the attacking forces in the described action or event.
-
E.
combatant2Commander
Indicates that a combatant serves under the authority or command of a specific commander.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
Created at: May 1, 2026, midnight