Triple
T13291509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaguar XK120 |
E316569
|
entity |
| Predicate | enginePowerOutput |
P6069
|
FINISHED |
| Object | 160 bhp |
—
|
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: 160 bhp | Statement: [Jaguar XK120, enginePowerOutput, 160 bhp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enginePowerOutput Context triple: [Jaguar XK120, enginePowerOutput, 160 bhp]
-
A.
enginePower
chosen
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
B.
designPowerOutput
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
C.
powerOutputRpm
Indicates the relationship between a system’s power output and the rotational speed (in revolutions per minute) at which that power is produced.
-
D.
powerOutputApprox
Indicates an approximate or estimated value for the power output produced by an entity or system.
-
E.
powerOutputType
Indicates the specific form or category of power output associated with an entity, such as electrical, mechanical, or thermal.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.