Triple
T13728035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Black Prince (1861) |
E329716
|
entity |
| Predicate | indicatedHorsepower |
P6069
|
FINISHED |
| Object | approximately 5400 ihp |
—
|
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: approximately 5400 ihp | Statement: [HMS Black Prince (1861), indicatedHorsepower, approximately 5400 ihp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatedHorsepower Context triple: [HMS Black Prince (1861), indicatedHorsepower, approximately 5400 ihp]
-
A.
horsepower
Indicates the power output or performance capacity associated with an entity, typically measuring how much work it can perform over time.
-
B.
enginePower
chosen
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
C.
vehiclePower
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
D.
engineDisplacement
Indicates the total volume swept by all the pistons inside an engine’s cylinders during one complete cycle.
-
E.
hasEngineDisplacementClass
Indicates a relationship where a vehicle or engine is assigned to a category based on the size or volume of its engine displacement.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f746cc8190abde237bbb7e6c78 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.