Triple
T16303113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24 Hours of Le Mans |
E395838
|
entity |
| Predicate | typicalRaceStartFormat |
P30569
|
FINISHED |
| Object | rolling start |
—
|
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: rolling start | Statement: [24 Hours of Le Mans, typicalRaceStartFormat, rolling start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRaceStartFormat Context triple: [24 Hours of Le Mans, typicalRaceStartFormat, rolling start]
-
A.
raceStartType
chosen
Indicates the manner or format in which a race is initiated (e.g., type or method of starting the race).
-
B.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
C.
raceAdded
Indicates that a race event or race-related record has been newly created or incorporated into a system or dataset.
-
D.
startedRacing
Indicates that an entity began participating in a racing activity or competition, marking the initiation of its involvement in racing.
-
E.
typicalRaceWeekendStructure
Indicates the usual sequence and organization of sessions and activities that make up a standard race weekend.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e35157481909e5604b7dae7a2a2 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.