Triple
T10471759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blériot XI |
E246938
|
entity |
| Predicate | laterPowerOutput |
P94210
|
FINISHED |
| Object | 50 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: 50 hp | Statement: [Blériot XI, laterPowerOutput, 50 hp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPowerOutput Context triple: [Blériot XI, laterPowerOutput, 50 hp]
-
A.
powerOutputApprox
Indicates an approximate or estimated value for the power output produced by an entity or system.
-
B.
transferredPowerTo
Indicates that one entity has passed control, authority, or energy to another entity.
-
C.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
D.
powerOutputType
Indicates the specific form or category of power output associated with an entity, such as electrical, mechanical, or thermal.
-
E.
designPowerOutput
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5094cec788190a485c5c9e7cd024a |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:20 p.m.