Triple
T25563202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO |
E640768
|
entity |
| Predicate | usesMilitaryCapability |
P159748
|
FINISHED |
| Object | air power |
—
|
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: air power | Statement: [NATO, usesMilitaryCapability, air power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMilitaryCapability Context triple: [NATO, usesMilitaryCapability, air power]
-
A.
militaryCapabilityInvolved
chosen
Indicates that a military capability (such as forces, equipment, or operational assets) participates in or is implicated in a specific event, activity, or situation.
-
B.
warfareCapability
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
-
C.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
D.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
E.
usesMilitarySystemSimilarTo
Indicates that one entity employs a military system that is comparable in structure, doctrine, or operational methods to that of another entity.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 3:47 p.m.