Triple
T32091241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Pulwama attack |
E819597
|
entity |
| Predicate | claimedByVideo |
P145857
|
FINISHED |
| Object | Jaish-e-Mohammed propaganda video |
—
|
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: Jaish-e-Mohammed propaganda video | Statement: [2019 Pulwama attack, claimedByVideo, Jaish-e-Mohammed propaganda video]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedByVideo Context triple: [2019 Pulwama attack, claimedByVideo, Jaish-e-Mohammed propaganda video]
-
A.
claimedAs
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
-
B.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
C.
claimedIn
chosen
Indicates that a statement, fact, or assertion is reported or documented within a particular source, document, or claim.
-
D.
claimed
Indicates that an entity has asserted or stated something as true, often without definitive proof or verification.
-
E.
claimedByAct
Indicates that an action or statement is attributed to, or asserted by, a particular agent 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 12:25 a.m.