Triple
T30492689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Kenley |
E775911
|
entity |
| Predicate | hasSurvivingFeature |
P89335
|
FINISHED |
| Object | blast pens |
—
|
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: blast pens | Statement: [RAF Kenley, hasSurvivingFeature, blast pens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurvivingFeature Context triple: [RAF Kenley, hasSurvivingFeature, blast pens]
-
A.
hasSurvivalElements
Indicates that something includes features or conditions related to survival, such as resource management, threat avoidance, or sustaining life over time.
-
B.
hasSurvivabilityFeature
Indicates that an entity possesses a characteristic, design element, or capability intended to enhance its ability to endure, resist damage, or remain functional under adverse conditions.
-
C.
hasSurvivingForm
Indicates that an entity continues to exist in some enduring, preserved, or currently observable form.
-
D.
hasSurvivors
Indicates that one or more entities continue to exist or remain alive after a particular event, condition, or incident.
-
E.
hasSurvivingElement
chosen
Indicates that an entity retains at least one remaining or extant part, instance, or component that still exists.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 29, 2026, 8:14 p.m.