Triple
T2978084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formula One |
E80445
|
entity |
| Predicate | raceWeekendStructure |
P35643
|
FINISHED |
| Object | practice sessions |
—
|
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: practice sessions | Statement: [Formula One, raceWeekendStructure, practice sessions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceWeekendStructure Context triple: [Formula One, raceWeekendStructure, practice sessions]
-
A.
raceDayIncludes
Indicates that a particular race day schedule or event set contains or encompasses a specific race or racing-related activity.
-
B.
raceMeeting
Indicates a competitive event where multiple participants race against each other under shared rules and conditions.
-
C.
seasonStructure
Indicates how a season is organized or structured in terms of its component parts, phases, or format.
-
D.
racingSeries
Indicates that one entity is a racing series in which the other entity (such as a race, team, or driver) participates or to which it belongs.
-
E.
competitionElement
chosen
Indicates that one entity is a component, phase, or sub-event within a larger competitive event or contest.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999b0d50819093dac7678b887a9b |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.