Triple
T2033563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upkeep bouncing bomb |
E44570
|
entity |
| Predicate | deploymentSpeed |
P35439
|
FINISHED |
| Object | about 220 miles per hour |
—
|
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: about 220 miles per hour | Statement: [Upkeep bouncing bomb, deploymentSpeed, about 220 miles per hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentSpeed Context triple: [Upkeep bouncing bomb, deploymentSpeed, about 220 miles per hour]
-
A.
migrationSpeed
Indicates the rate at which an entity moves from one location or region to another over a given period of time.
-
B.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
C.
deploys
Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
-
D.
deploymentRequires
Indicates that performing a particular deployment is contingent upon the prior existence, completion, or availability of another specified resource, condition, or action.
-
E.
deploymentModel
Indicates the type or manner in which a system, service, or resource is deployed or made available (e.g., on-premises, cloud, hybrid).
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb93255248190bd47a54a7b3c7447 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb90ec7948190bbfb0329e9e67cca |
completed | March 7, 2026, 5:35 a.m. |
Created at: March 4, 2026, 7:39 p.m.