Triple
T35753232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Grand Prix |
E1033371
|
entity |
| Predicate | grandPrixType |
P118545
|
FINISHED |
| Object | pre-World Championship Grand Prix |
—
|
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: pre-World Championship Grand Prix | Statement: [Swiss Grand Prix, grandPrixType, pre-World Championship Grand Prix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandPrixType Context triple: [Swiss Grand Prix, grandPrixType, pre-World Championship Grand Prix]
-
A.
grandPrixClass
chosen
Indicates that something belongs to, competes in, or is categorized under a specific Grand Prix racing class or division.
-
B.
grandPrixName
Indicates the official name assigned to a particular Grand Prix event.
-
C.
GrandPrixTitle
Indicates that an entity has won a championship or overall title in a Grand Prix competition or series.
-
D.
homeGrandPrix
Indicates that a particular Grand Prix event is considered the home race for a given driver, team, or country.
-
E.
GrandTour
Indicates a comprehensive, often extended journey or series of visits undertaken to explore multiple places, typically for cultural, educational, or experiential purposes.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:06 p.m.