Triple
T7531545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Russian Grand Prix |
E178033
|
entity |
| Predicate | fastestLapTime |
P77656
|
FINISHED |
| Object | 1:40.896 |
—
|
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: 1:40.896 | Statement: [2014 Russian Grand Prix, fastestLapTime, 1:40.896]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastestLapTime Context triple: [2014 Russian Grand Prix, fastestLapTime, 1:40.896]
-
A.
totalFormulaOneFastestLaps
Indicates the total number of fastest laps a driver (or team) has recorded in Formula One races.
-
B.
safetyCarLapRecordHolder
Indicates that one entity holds the record for the most notable or fastest performance during a lap completed under safety car conditions in a race.
-
C.
F1LapRecordHolder
Indicates that the subject holds the fastest lap record in a Formula 1 race or at a specific Formula 1 circuit.
-
D.
maximumSpeedRecord
Indicates that an entity holds the highest recorded speed value (a speed record) within a given context or category.
-
E.
F1LapRecordCar
Indicates the car that holds the lap record in a Formula 1 session or at a specific F1 circuit.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8217b1c8190b3db453cee0fc4fd |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f5cea2748190afd607ef93e8d66c |
completed | March 27, 2026, 9:25 p.m. |
Created at: March 27, 2026, 3:47 p.m.