Triple
T4424340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prompt Global Strike |
E95174
|
entity |
| Predicate | capabilityType |
P55904
|
FINISHED |
| Object | conventional precision strike |
—
|
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: conventional precision strike | Statement: [Prompt Global Strike, capabilityType, conventional precision strike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capabilityType Context triple: [Prompt Global Strike, capabilityType, conventional precision strike]
-
A.
consideredCapability
Indicates that something is regarded or evaluated as a potential capability of an entity.
-
B.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
C.
couplingCapability
Indicates the ability or suitability of one entity to connect, link, or interface with another in a functional or compatible manner.
-
D.
plannedCapability
Indicates that an entity is intended or scheduled to possess or provide a particular capability in the future.
-
E.
usedCapability
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
- F. None of above. chosen
Provenance (4 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554ca5208190ba2661616dcf071c |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:30 p.m.