Triple
T31704615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAAMS missiles |
E809144
|
entity |
| Predicate | defenceLayer |
P32381
|
FINISHED |
| Object | outer air battle |
—
|
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: outer air battle | Statement: [PAAMS missiles, defenceLayer, outer air battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenceLayer Context triple: [PAAMS missiles, defenceLayer, outer air battle]
-
A.
defenseLayer
chosen
Indicates a protective barrier or mechanism that shields an entity from harm, attack, or unwanted influence.
-
B.
providesDefence
Indicates that one entity offers protection or defensive support to another entity.
-
C.
defensiveStructure
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
-
D.
defenceBody
Indicates a relationship where an entity serves as the official body or organization responsible for defense or military affairs of another entity (such as a country or jurisdiction).
-
E.
defensiveSystem
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 30, 2026, 11:13 p.m.