Triple
T27376686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Acklington |
E691092
|
entity |
| Predicate | airDefenceRole |
P9463
|
FINISHED |
| Object | protection of North-East England |
—
|
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: protection of North-East England | Statement: [RAF Acklington, airDefenceRole, protection of North-East England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airDefenceRole Context triple: [RAF Acklington, airDefenceRole, protection of North-East England]
-
A.
airDefenseSystem
Indicates a defensive military system designed to detect, track, and engage airborne threats such as aircraft or missiles.
-
B.
airDefenseSystemComponent
Indicates that one entity is a component or subsystem of an air defense system associated with another entity.
-
C.
airDefenseArmament
Indicates the weapons or systems specifically equipped on an entity for defending against aerial threats such as aircraft or missiles.
-
D.
airfieldDefended
Indicates that defensive measures or forces are in place to protect an airfield from attack or unauthorized intrusion.
-
E.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
- 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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62c839c588190ad8297d0b5637d12 |
completed | May 2, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:21 p.m.