Triple
T28107489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2004 Formula One World Championship |
E710401
|
entity |
| Predicate | safetyCarRegulations |
P167797
|
FINISHED |
| Object | revised safety car restart procedures |
—
|
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: revised safety car restart procedures | Statement: [2004 Formula One World Championship, safetyCarRegulations, revised safety car restart procedures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyCarRegulations Context triple: [2004 Formula One World Championship, safetyCarRegulations, revised safety car restart procedures]
-
A.
safetyCarFrequency
Indicates how often a safety car is deployed or appears within a given context or time frame.
-
B.
safetyCarUsed
Indicates that a safety car was deployed and used during an event or activity.
-
C.
safetyCarPeriods
Indicates periods during an event when a safety car is deployed, affecting normal progression or conditions.
-
D.
safetyCarPossible
Indicates that conditions are such that deploying a safety car is a valid or allowable option.
-
E.
safetyCarStart
Indicates that a safety car period has begun, initiating the deployment of the safety car onto the track.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 27, 2026, 9:09 p.m.