Triple
T16145633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daytona Supercross |
E391772
|
entity |
| Predicate | hasOfficialTimingBy |
P5062
|
FINISHED |
| Object | AMA timing and scoring systems |
—
|
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: AMA timing and scoring systems | Statement: [Daytona Supercross, hasOfficialTimingBy, AMA timing and scoring systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialTimingBy Context triple: [Daytona Supercross, hasOfficialTimingBy, AMA timing and scoring systems]
-
A.
isOfficialFinishFor
Indicates that one event, result, or record serves as the formally recognized completion point for another process, activity, or competition.
-
B.
hasOfficialDuration
Indicates the formally defined length of time associated with an event, process, or entity.
-
C.
usedAsOfficialTime
chosen
Indicates that something is employed as the recognized standard or authoritative reference for measuring time in an official context.
-
D.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
E.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9376fc8190bd9ef586b00c1d3b |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.