Triple
T29526755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford flathead V8 |
E749088
|
entity |
| Predicate | firstProductionHorsepower |
P5894
|
FINISHED |
| Object | 65 horsepower |
—
|
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: 65 horsepower | Statement: [Ford flathead V8, firstProductionHorsepower, 65 horsepower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstProductionHorsepower Context triple: [Ford flathead V8, firstProductionHorsepower, 65 horsepower]
-
A.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
B.
horsepower
chosen
Indicates the power output or performance capacity associated with an entity, typically measuring how much work it can perform over time.
-
C.
firstGenerationEngine
Indicates that the engine belongs to the first generation in a series of engine designs or development iterations.
-
D.
vehiclePower
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
E.
maximumTurboPower
Indicates the highest level of turbo power that can be achieved or utilized in the given context.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a00d76d0e0881908d83a8dcce511167 |
completed | May 10, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a00d711805881909a94cfd1f25fb331 |
completed | May 10, 2026, 7:05 p.m. |
Created at: April 28, 2026, 4:47 p.m.