Triple
T20667242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infiniti Q60 |
E507923
|
entity |
| Predicate | highPerformancePowerOutput |
P84509
|
FINISHED |
| Object | 400 hp (approximate) |
—
|
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: 400 hp (approximate) | Statement: [Infiniti Q60, highPerformancePowerOutput, 400 hp (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highPerformancePowerOutput Context triple: [Infiniti Q60, highPerformancePowerOutput, 400 hp (approximate)]
-
A.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
B.
powerOutputType
Indicates the specific form or category of power output associated with an entity, such as electrical, mechanical, or thermal.
-
C.
powerOutput_kW
Indicates the amount of power produced or delivered by something, measured in kilowatts.
-
D.
laterPowerOutput
Indicates that the power output of an entity at a later time is being related or compared to its power output at an earlier time.
-
E.
powerOutputApprox
chosen
Indicates an approximate or estimated value for the power output produced by an entity or system.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c39dd48190965d65537592aef6 |
completed | April 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.