Triple
T38174480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ababeel |
E1000166
|
entity |
| Predicate | statusOfMIRVCapability |
P105674
|
FINISHED |
| Object | claimed by Pakistan |
—
|
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: claimed by Pakistan | Statement: [Ababeel, statusOfMIRVCapability, claimed by Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfMIRVCapability Context triple: [Ababeel, statusOfMIRVCapability, claimed by Pakistan]
-
A.
MIRVStatus
chosen
Indicates the status or condition of a multiple independently targetable reentry vehicle (MIRV) capability associated with a given entity or system.
-
B.
supportsMirrorMode
Indicates that one entity provides the capability for another entity or process to operate in a mirror or mirrored-display mode.
-
C.
hasFeatureStatus
Indicates that an entity possesses a particular feature along with its current state or condition.
-
D.
demonstratedCapability
Indicates that an entity has shown, through evidence or performance, the ability to carry out a specific action or function.
-
E.
detectorCapability
Indicates that one entity has the ability or functional capacity to detect, sense, or identify another entity or phenomenon.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: May 3, 2026, 4:29 p.m.