Triple
T32424826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suzuka 8 Hours |
E828548
|
entity |
| Predicate | typicalRaceEndTime |
P47077
|
FINISHED |
| Object | after sunset |
—
|
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: after sunset | Statement: [Suzuka 8 Hours, typicalRaceEndTime, after sunset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRaceEndTime Context triple: [Suzuka 8 Hours, typicalRaceEndTime, after sunset]
-
A.
typicalRaceLengthCategory
Indicates the usual distance range or length classification that a race is most commonly run at.
-
B.
timingOfRace
chosen
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
C.
approximateRaceLength
Indicates that one entity specifies an estimated or rough value for the length or distance of a race associated with another entity.
-
D.
raceWinningTime_hours
Indicates the duration, measured in hours, that it took the winning participant to complete the race.
-
E.
typicalRaceDistanceUnit
Indicates the standard unit of measurement used to express the usual race distance associated with an entity.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:54 a.m.