Triple
T16781693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Ceptor |
E407870
|
entity |
| Predicate | defenceType |
P1135
|
FINISHED |
| Object | local area air defence |
—
|
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: local area air defence | Statement: [Sea Ceptor, defenceType, local area air defence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenceType Context triple: [Sea Ceptor, defenceType, local area air defence]
-
A.
typeOfDefense
chosen
Indicates the specific kind or category of defense employed or possessed in a given context.
-
B.
defenceHandledBy
Indicates that responsibility for managing or conducting a defence is assigned to or carried out by a particular agent or entity.
-
C.
defensiveSystem
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
-
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.
defensiveStructure
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b216726881908ddc9cdc772cd5e4 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.