Triple
T16741355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CH-47F Chinook |
E406840
|
entity |
| Predicate | hasSelfProtection |
P20171
|
FINISHED |
| Object | missile warning system |
—
|
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: missile warning system | Statement: [CH-47F Chinook, hasSelfProtection, missile warning system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSelfProtection Context triple: [CH-47F Chinook, hasSelfProtection, missile warning system]
-
A.
providesProtectionIn
Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
-
B.
providesProtectionAgainst
chosen
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
-
C.
hasProtectionPurpose
Indicates that something is intended or designed to serve a protective function or goal.
-
D.
hasProtectionEffort
Indicates that an entity undertakes or is subject to actions or measures aimed at protecting or conserving another entity.
-
E.
coreProtection
Indicates that an entity provides essential safeguarding or defense for another entity’s central or most critical component.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3e87348190acaf7c40e8f8b566 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.