Triple
T35752485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 British Grand Prix |
E1033352
|
entity |
| Predicate | grandPrixHeldAtCircuit |
P120093
|
FINISHED |
| Object | Silverstone Circuit |
—
|
NE NERFINISHED |
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: Silverstone Circuit | Statement: [2016 British Grand Prix, grandPrixHeldAtCircuit, Silverstone Circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandPrixHeldAtCircuit Context triple: [2016 British Grand Prix, grandPrixHeldAtCircuit, Silverstone Circuit]
-
A.
grandPrixName
Indicates the official name assigned to a particular Grand Prix event.
-
B.
GrandPrixCircuitLengthKm
Indicates the total length, measured in kilometers, of a Grand Prix racing circuit.
-
C.
homeGrandPrix
Indicates that a particular Grand Prix event is considered the home race for a given driver, team, or country.
-
D.
formerF1Venue
Indicates that a location previously hosted Formula 1 races but is no longer an active venue for the championship.
-
E.
hadGrandPrix
chosen
Indicates that a particular Grand Prix event took place as part of, or was hosted by, a given competition, season, or venue.
- 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_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.