Triple
T209423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomahawk cruise missile |
E4680
|
entity |
| Predicate | launchWeight |
P7196
|
FINISHED |
| Object | approximately 1,300 kilograms |
—
|
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: approximately 1,300 kilograms | Statement: [Tomahawk cruise missile, launchWeight, approximately 1,300 kilograms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchWeight Context triple: [Tomahawk cruise missile, launchWeight, approximately 1,300 kilograms]
-
A.
launchMass
chosen
Indicates the total mass of an object or payload at the moment it is launched.
-
B.
launchVehicle
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
C.
weight
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
D.
landingGear
Indicates that an entity’s landing gear is present, deployed, or otherwise involved in a landing-related state or action relative to another entity or context.
-
E.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e8b9b908190b69a3f0594b95f7e |
completed | Feb. 28, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69a25b4e3c2881908d83e8218aa9f2d9 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.