Triple
T24791697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GT Daytona |
E620267
|
entity |
| Predicate | typicalDriverRatings |
P165799
|
FINISHED |
| Object | Bronze |
—
|
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: Bronze | Statement: [GT Daytona, typicalDriverRatings, Bronze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDriverRatings Context triple: [GT Daytona, typicalDriverRatings, Bronze]
-
A.
featuresDrivers
Indicates that something includes or highlights specific drivers as notable components or participants.
-
B.
timeformRating
Indicates the performance quality or ability of an entity as measured by a specific time-based rating or scoring system.
-
C.
bestDriver
Indicates that the subject is considered the most skilled or highest-performing driver within a specified group or context.
-
D.
drivingDiscipline
Indicates the manner and quality of how an entity operates a vehicle, especially in terms of adherence to traffic rules and safe driving behavior.
-
E.
racingDriver
Indicates that one entity is a racing driver, i.e., a person who competes in motor races as a driver.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a9cb0bc8190bf8a9b319900bad5 |
completed | May 2, 2026, 8:12 p.m. |
Created at: April 18, 2026, 4:47 a.m.