Triple
T24791881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebring International Raceway |
E620271
|
entity |
| Predicate | first12HoursOfSebringHeld |
P163663
|
FINISHED |
| Object | 1952 |
—
|
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: 1952 | Statement: [Sebring International Raceway, first12HoursOfSebringHeld, 1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: first12HoursOfSebringHeld Context triple: [Sebring International Raceway, first12HoursOfSebringHeld, 1952]
-
A.
firstHeldAs24HourRace
Indicates that the event was first conducted in the format of a continuous 24-hour race.
-
B.
firstNASCARStart
Indicates the event or record marking when an entity (typically a driver) made their first competitive start in a NASCAR race or series.
-
C.
firstCupRace
Indicates the inaugural or earliest cup race event associated with the given entity or context.
-
D.
firstIndyCarSeriesRace
Indicates the event that was a subject's first race participation in the IndyCar Series.
-
E.
first120MphLapTeam
Indicates the team that first completed a lap at a speed of 120 miles per hour.
- 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_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638d029148190877c103f0eeaf147 |
completed | May 2, 2026, 5:48 p.m. |
Created at: April 18, 2026, 4:47 a.m.