Triple
T20129371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalibr cruise missile |
E490846
|
entity |
| Predicate | terminalSpeed |
P138784
|
FINISHED |
| Object | supersonic in some anti-ship variants |
—
|
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: supersonic in some anti-ship variants | Statement: [Kalibr cruise missile, terminalSpeed, supersonic in some anti-ship variants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalSpeed Context triple: [Kalibr cruise missile, terminalSpeed, supersonic in some anti-ship variants]
-
A.
lineSpeedContext
Indicates the contextual conditions or parameters under which a particular line speed is defined, measured, or applied.
-
B.
recommendedSpeed
Indicates the speed that is advised or suggested as appropriate under given conditions, rather than required or actual speed.
-
C.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
D.
currentSpeed
Indicates the present rate at which an entity is moving over time.
-
E.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
- F. None of above. chosen
Provenance (4 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66760b8f08190a66fbb2e9e3925a3 |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:31 p.m.