Triple
T16773162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriot |
E407651
|
entity |
| Predicate | canIntercept |
P32377
|
FINISHED |
| Object | aircraft |
—
|
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: aircraft | Statement: [Patriot, canIntercept, aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canIntercept Context triple: [Patriot, canIntercept, aircraft]
-
A.
designedToIntercept
chosen
Indicates that one entity is purposefully created or configured to detect, block, or otherwise interrupt the actions, movement, or effects of another entity.
-
B.
canHandle
Indicates that an entity has the ability or capacity to manage, process, or deal with another entity or situation.
-
C.
interceptionMethod
Indicates the technique or means by which an interception (such as capturing data, signals, or communications) is carried out.
-
D.
canPerform
Indicates that one entity has the ability, permission, or capacity to carry out a specific action or function on or with another entity.
-
E.
canBlock
Indicates that one entity has the ability or permission to prevent, obstruct, or stop the action or effect of another entity.
- 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_69e3b037c5708190ba604e7707b5a8a2 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.