Triple
T32424742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Grand Prix |
E828547
|
entity |
| Predicate | heldAtCircuit |
P133058
|
FINISHED |
| Object | Fuji Speedway |
—
|
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: Fuji Speedway | Statement: [Japanese Grand Prix, heldAtCircuit, Fuji Speedway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldAtCircuit Context triple: [Japanese Grand Prix, heldAtCircuit, Fuji Speedway]
-
A.
hostedByCircuit
chosen
Indicates that an event, activity, or process is organized, managed, or carried out under the responsibility or auspices of a particular circuit.
-
B.
circuitHolding
Indicates that one entity is physically grasping, supporting, or maintaining control of an electrical circuit or circuit component.
-
C.
performingCircuit
Indicates that an entity is carrying out or executing a specific circuit, such as a sequence of connected paths, routes, or tasks.
-
D.
raceWinCircuit
Indicates that an entity wins a race that takes place on a specific circuit.
-
E.
heldByRace
Indicates that something (such as an event, title, or position) is organized, controlled, or hosted by a particular race or racial group.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c286ac288190843dac21651babd0 |
completed | May 3, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:54 a.m.