Triple
T15437621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4.6 L Northstar V8 |
E369807
|
entity |
| Predicate | maxPowerOutput |
P18504
|
FINISHED |
| Object | up to about 320 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: up to about 320 hp | Statement: [4.6 L Northstar V8, maxPowerOutput, up to about 320 hp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxPowerOutput Context triple: [4.6 L Northstar V8, maxPowerOutput, up to about 320 hp]
-
A.
powerOutput_kW
Indicates the amount of power produced or delivered by something, measured in kilowatts.
-
B.
designPowerOutput
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
C.
maximumPowerDuringOperation
chosen
Indicates the highest level of power that occurs while the system or component is operating.
-
D.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
E.
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.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03edca064819081510bf303271062 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.