Triple
T201656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Merlin |
E4518
|
entity |
| Predicate | typicalPowerOutput |
P6069
|
FINISHED |
| Object | 1000 to 1700 horsepower |
—
|
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: 1000 to 1700 horsepower | Statement: [Rolls-Royce Merlin, typicalPowerOutput, 1000 to 1700 horsepower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPowerOutput Context triple: [Rolls-Royce Merlin, typicalPowerOutput, 1000 to 1700 horsepower]
-
A.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
B.
pumpingPower
Indicates the rate at which energy is supplied or transferred by a pump to move a fluid or medium.
-
C.
enginePower
chosen
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
D.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
E.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
- 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_69a25c2ead8481909996042efcae5e9d |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b4a0d448190a6fa6aeb30dc7e13 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.