Triple
T20322115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-400 missile system |
E492230
|
entity |
| Predicate | canEngageMultipleTargetsSimultaneously |
P39122
|
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: [S-400 missile system, canEngageMultipleTargetsSimultaneously, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canEngageMultipleTargetsSimultaneously Context triple: [S-400 missile system, canEngageMultipleTargetsSimultaneously, yes]
-
A.
designedToFireSimultaneously
Indicates that multiple entities are configured or intended to operate or be activated at the same time.
-
B.
hasMultipleHoldersSimultaneously
Indicates that a given item, role, or resource is concurrently possessed, controlled, or occupied by more than one holder at the same time.
-
C.
isCapableOf
chosen
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
D.
canOperateInMultiple
Indicates that an entity is capable of functioning or being used across more than one context, environment, or mode.
-
E.
supportsMultipleMotorOutputs
Indicates that the subject is capable of driving or controlling more than one motor output simultaneously or in parallel.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778c4430819083b17da5067b88ef |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:20 a.m.