Triple
T2675461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beechcraft C-45 Expeditor |
E56447
|
entity |
| Predicate | powerplantOutput |
P41620
|
FINISHED |
| Object | about 450 hp each |
—
|
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 450 hp each | Statement: [Beechcraft C-45 Expeditor, powerplantOutput, about 450 hp each]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerplantOutput Context triple: [Beechcraft C-45 Expeditor, powerplantOutput, about 450 hp each]
-
A.
powerplant
Indicates that an entity functions as a facility or installation where energy sources are converted into usable power, typically electricity.
-
B.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
-
C.
powerplantFor
Indicates that one entity functions as the power plant or primary energy source serving another entity.
-
D.
powerplantRole
Indicates that one entity serves in a specific functional or operational role relative to a power plant.
-
E.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9b3530c819093942cc985f814ef |
completed | March 7, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8f98c348190a68064c565589459 |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:54 p.m.