Triple
T36075455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Grand Prix |
E1043483
|
entity |
| Predicate | firstWorldChampionshipWinner |
P108701
|
FINISHED |
| Object | Giuseppe Farina |
E1033338
|
NE 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: Giuseppe Farina | Statement: [British Grand Prix, firstWorldChampionshipWinner, Giuseppe Farina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstWorldChampionshipWinner Context triple: [British Grand Prix, firstWorldChampionshipWinner, Giuseppe Farina]
-
A.
worldChampionPredecessor
Indicates that one entity was the immediate previous world champion before another entity.
-
B.
firstWinnerYear
Indicates the year in which an entity first won a particular competition, award, or title.
-
C.
worldChampionIn
Indicates that an entity holds or has held the title of world champion in a specified field, discipline, or competition.
-
D.
firstChampions
chosen
Indicates that the subject entities are the initial or earliest champions (winners or title holders) in a given competition, event, or context.
-
E.
featuredWorldChampion
Indicates that an entity has been highlighted or showcased specifically in its capacity as a world champion.
- F. None of above.
Provenance (4 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4095137cfc8190bd65e0a7859092f5 |
completed | June 28, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.