Triple
T31903174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Uri attack |
E814476
|
entity |
| Predicate | allegedOriginOfAttackers |
P150760
|
FINISHED |
| Object | Pakistan-administered Kashmir |
—
|
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: Pakistan-administered Kashmir | Statement: [2016 Uri attack, allegedOriginOfAttackers, Pakistan-administered Kashmir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedOriginOfAttackers Context triple: [2016 Uri attack, allegedOriginOfAttackers, Pakistan-administered Kashmir]
-
A.
countryOfOriginOfAttackers
chosen
Indicates the country from which the attackers originated or are associated in the context of an attack.
-
B.
attackedFrom
Indicates that one entity initiated an attack against another entity originating from a specific source location or position.
-
C.
attackingAircraftOrigin
Indicates that one entity is the place or source from which an attacking aircraft originates.
-
D.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
E.
objectiveOfAttackers
Indicates the target or goal that attackers aim to reach or affect through their attack.
- 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_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, midnight