Triple
T16295570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Coningsby |
E395636
|
entity |
| Predicate | hasHardenedAircraftShelters |
P59811
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [RAF Coningsby, hasHardenedAircraftShelters, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHardenedAircraftShelters Context triple: [RAF Coningsby, hasHardenedAircraftShelters, yes]
-
A.
hasHardenedShelters
chosen
Indicates that an entity possesses or is equipped with shelters that are reinforced or hardened for protection.
-
B.
hasBunkers
Indicates that one entity possesses or contains bunkers, such as fortified shelters or storage structures, as part of its features or infrastructure.
-
C.
hasTacticalAviationFacilities
Indicates that an entity possesses or hosts infrastructure and resources specifically designated for tactical aviation operations.
-
D.
hasShelteredAreas
Indicates that one entity provides or contains areas that offer protection or cover for another entity.
-
E.
airDefenseArmament
Indicates the weapons or systems specifically equipped on an entity for defending against aerial threats such as aircraft or missiles.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2d08108190bab1b3325923af1d |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.