Triple
T10982179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sopwith 1½ Strutter |
E259534
|
entity |
| Predicate | typicalEnginePower |
P89369
|
FINISHED |
| Object | 130 hp |
—
|
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: 130 hp | Statement: [Sopwith 1½ Strutter, typicalEnginePower, 130 hp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEnginePower Context triple: [Sopwith 1½ Strutter, typicalEnginePower, 130 hp]
-
A.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
B.
vehiclePower
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
C.
typicalPower
chosen
Indicates the usual or characteristic amount of power associated with an entity under normal operating conditions.
-
D.
horsepower
Indicates the power output or performance capacity associated with an entity, typically measuring how much work it can perform over time.
-
E.
powerRange
Indicates the range of power values within which an entity operates, applies, or is considered valid.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772eb518c8190a885a417815f2ff6 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.