Triple
T38327761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Circuit |
E1036836
|
entity |
| Predicate | firstUsedForFormulaOneSeason |
P130664
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [International Circuit, firstUsedForFormulaOneSeason, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUsedForFormulaOneSeason Context triple: [International Circuit, firstUsedForFormulaOneSeason, 2010]
-
A.
firstUsedForFormulaOneWorldChampionship
chosen
Indicates that something (typically a circuit, track, or venue) was used for the first time in hosting a Formula One World Championship event.
-
B.
firstF1Season
Indicates the Formula 1 season in which an entity (typically a driver or team) first competed.
-
C.
grandPrixDebutYear
Indicates the year in which an entity first participated in a Grand Prix event.
-
D.
debutInFormulaOneSeason
Indicates the Formula One season during which an entity (typically a driver or team) made its first official appearance in the championship.
-
E.
madeF1DebutForTeam
Indicates that a driver’s first-ever Formula 1 race appearance was made while competing for the specified team.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.