Triple
T19689802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Grand Prix |
E472803
|
entity |
| Predicate | hasSprintRacesInSomeSeasons |
P126991
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Italian Grand Prix, hasSprintRacesInSomeSeasons, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSprintRacesInSomeSeasons Context triple: [Italian Grand Prix, hasSprintRacesInSomeSeasons, true]
-
A.
hasSprintRaceInSomeYears
chosen
Indicates that the associated entity has held or will hold a sprint race in at least one, but not necessarily all, of the years in question.
-
B.
isSprintChampionshipRace
Indicates that the race is designated as the sprint championship event within a competition or season.
-
C.
hadNonChampionshipRaces
Indicates that the subject participated in races that were not part of a championship series or title competition.
-
D.
racedInSeries
Indicates that an entity participated as a competitor in a particular racing series or championship.
-
E.
hasRacingDiscipline
Indicates that an entity participates in, is associated with, or is characterized by a specific type or category of racing discipline.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420f1a0c8190ae59aa0ab3ff2802 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.