Triple
T29526781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford flathead V8 |
E749088
|
entity |
| Predicate | typicalRedline |
P176998
|
FINISHED |
| Object | approximately 3500 to 4000 rpm |
—
|
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 3500 to 4000 rpm | Statement: [Ford flathead V8, typicalRedline, approximately 3500 to 4000 rpm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRedline Context triple: [Ford flathead V8, typicalRedline, approximately 3500 to 4000 rpm]
-
A.
redline
Indicates the act of refusing to offer services, opportunities, or fair treatment to certain people or areas based on discriminatory criteria such as race or neighborhood.
-
B.
typicalStyleRed
Indicates that something commonly or characteristically has a red style or appearance.
-
C.
typicalRedStyleDescriptor
Indicates that something is described as having the characteristic or stylistic qualities typically associated with the color red.
-
D.
typicalRedProfile
Indicates that an entity exhibits a characteristic or standard pattern commonly associated with the color red.
-
E.
engineRedline
chosen
Indicates the maximum engine speed limit at which the engine can safely operate before risking damage.
- 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_6a01d339feac8190a3de56b24db67163 |
completed | May 11, 2026, 1:01 p.m. |
| PD | Predicate disambiguation | batch_6a01d2bc1f408190a04869f95e6941ee |
completed | May 11, 2026, 12:59 p.m. |
Created at: April 28, 2026, 4:47 p.m.