Triple
T32424740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Grand Prix |
E828547
|
entity |
| Predicate | firstWorldChampionshipEventAtCircuit |
P126981
|
FINISHED |
| Object | Fuji Speedway |
E713424
|
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: Fuji Speedway | Statement: [Japanese Grand Prix, firstWorldChampionshipEventAtCircuit, Fuji Speedway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstWorldChampionshipEventAtCircuit Context triple: [Japanese Grand Prix, firstWorldChampionshipEventAtCircuit, Fuji Speedway]
-
A.
firstRaceAtCircuit
chosen
Indicates that the referenced race is the first race ever held at the specified circuit.
-
B.
firstF1RaceHeld
Indicates that the subject is the location or venue where the first Formula 1 race was held.
-
C.
firstChampionshipWinEvent
Indicates the event in which an entity achieves its first-ever championship victory.
-
D.
mostFamousCircuit
Indicates that one circuit is considered the most famous or well-known among a relevant set of circuits.
-
E.
grandPrixNumberAtCircuit
Indicates the ordinal number of the Grand Prix event held at a specific circuit within a series or season.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a344f28cc3c8190894ce0c64aca697d |
completed | June 18, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:54 a.m.