Triple
T10786847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5.2L Voodoo V8 |
E254472
|
entity |
| Predicate | redline |
P95476
|
FINISHED |
| Object | 8250 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: 8250 rpm | Statement: [5.2L Voodoo V8, redline, 8250 rpm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redline Context triple: [5.2L Voodoo V8, redline, 8250 rpm]
-
A.
criticalLine
Indicates that one entity is a crucial or decisive line (such as a boundary, path, or threshold) whose state or position significantly affects the other entity or overall system.
-
B.
yardLine
Indicates the specific position on a football field, measured in yards from a reference goal line, where a play or event occurs.
-
C.
divisionLine
Indicates a boundary or separating line that divides one area, group, or portion from another.
-
D.
lineStandard
Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
-
E.
lining
Indicates that one entity forms a layer or covering along the inner or outer surface of another entity.
- F. None of above. chosen
Provenance (4 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d5422481908d7ab833c6cbc879 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:17 p.m.