Triple
T17321795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Grand Prix |
E420578
|
entity |
| Predicate | firstHeldAsWorldChampionshipEvent |
P27044
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [United States Grand Prix, firstHeldAsWorldChampionshipEvent, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHeldAsWorldChampionshipEvent Context triple: [United States Grand Prix, firstHeldAsWorldChampionshipEvent, 1959]
-
A.
firstHeldAsWorldChampionshipRound
chosen
Indicates the event or race at which a competition was first officially held as a round of the world championship.
-
B.
firstChampionshipWinEvent
Indicates the event in which an entity achieves its first-ever championship victory.
-
C.
championshipHeld
Indicates that a championship event took place or was hosted at a particular time and/or location.
-
D.
firstHeldAsSeparateTournament
Indicates that an event was initially conducted as an independent, standalone tournament rather than as part of another competition.
-
E.
championshipHeldIn
Indicates that a particular championship event takes place or is hosted in a specific location.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d01e2c8190a358dace420d4575 |
completed | April 19, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.