Triple
T209421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomahawk cruise missile |
E4680
|
entity |
| Predicate | powerplant |
P9904
|
FINISHED |
| Object | Williams International turbofan engine |
—
|
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: Williams International turbofan engine | Statement: [Tomahawk cruise missile, powerplant, Williams International turbofan engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerplant Context triple: [Tomahawk cruise missile, powerplant, Williams International turbofan engine]
-
A.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
B.
mainCentralPower
Indicates that an entity functions as the primary central authority or dominant power within a given system or context.
-
C.
plannedFacility
Indicates that a facility is intended or scheduled to be built, established, or implemented in the future but does not yet exist or operate.
-
D.
electrificationSystem
Indicates the type of electrical power system used to supply energy (typically to infrastructure or vehicles) for operation.
-
E.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
- 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_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. |
| PDg | Predicate description generation | batch_69a25e8ade9481908d5570f6a255ee50 |
completed | Feb. 28, 2026, 3:18 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.