Triple
T33139686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aston Martin Valkyrie |
E848107
|
entity |
| Predicate | engineRedline |
P176998
|
FINISHED |
| Object | around 11000 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: around 11000 rpm | Statement: [Aston Martin Valkyrie, engineRedline, around 11000 rpm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineRedline Context triple: [Aston Martin Valkyrie, engineRedline, around 11000 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.
engineBase
Indicates that one entity serves as the foundational or primary engine upon which another engine or engine-related component is built or derived.
-
C.
engineCode
Indicates a relationship where an entity is associated with a specific engine identification code or designation.
-
D.
engineIntroduced
Indicates that a particular engine was first introduced or brought into use at a specific time or in a specific context.
-
E.
developedEngine
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f814fcf48190ae4504154d1b2c05 |
completed | May 3, 2026, 7:24 a.m. |
Created at: May 1, 2026, 1:27 a.m.