Triple
T12266535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrow missile system |
E292360
|
entity |
| Predicate | typeOfInterceptor |
P71000
|
FINISHED |
| Object | surface-to-air missile |
—
|
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: surface-to-air missile | Statement: [Arrow missile system, typeOfInterceptor, surface-to-air missile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfInterceptor Context triple: [Arrow missile system, typeOfInterceptor, surface-to-air missile]
-
A.
interceptorType
chosen
Indicates the specific kind or category of interceptor involved in the relationship or action.
-
B.
interceptorBasing
Indicates the basing or stationing relationship between interceptor units and the locations or facilities from which they operate.
-
C.
designedToIntercept
Indicates that one entity is purposefully created or configured to detect, block, or otherwise interrupt the actions, movement, or effects of another entity.
-
D.
typeOfAspect
Indicates that one aspect is a specific kind or category of another, more general aspect.
-
E.
intermediaryType
Indicates the specific role or category of intermediary involved in facilitating the relationship or transaction between entities.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.