Triple
T24791773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daytona Prototype international |
E620268
|
entity |
| Predicate | engineConfigurationRange |
P56053
|
FINISHED |
| Object | various V6 and V8 engines |
—
|
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: various V6 and V8 engines | Statement: [Daytona Prototype international, engineConfigurationRange, various V6 and V8 engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineConfigurationRange Context triple: [Daytona Prototype international, engineConfigurationRange, various V6 and V8 engines]
-
A.
engineConfigurationSupport
chosen
Indicates that one entity provides or defines support for a particular engine configuration of another entity.
-
B.
tuningRange
Indicates the range of values over which something can be tuned or adjusted.
-
C.
governingSpeedRange
Indicates the range of speeds within which a governing or limiting mechanism is intended to operate or apply.
-
D.
operationalRange
Indicates the span of conditions (such as distance, time, or environment) within which a system, device, or process can function effectively and safely.
-
E.
controlRange
Indicates the spatial or contextual extent within which an entity can exert control or influence over another entity or process.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4110424188190889a13976b16b18a |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:47 a.m.