Triple
T35753200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Grand Prix |
E1033370
|
entity |
| Predicate | sawMoveOfMainVenueFrom |
P13839
|
FINISHED |
| Object | Nürburgring Nordschleife |
—
|
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: Nürburgring Nordschleife | Statement: [German Grand Prix, sawMoveOfMainVenueFrom, Nürburgring Nordschleife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawMoveOfMainVenueFrom Context triple: [German Grand Prix, sawMoveOfMainVenueFrom, Nürburgring Nordschleife]
-
A.
replacedVenue
Indicates that one venue has taken the place of another as its successor location or site.
-
B.
formerVenueComponentOf
Indicates that a venue previously functioned as a component or part of a larger venue or venue complex, but no longer holds that status.
-
C.
rescheduledVenue
Indicates that the location or venue for an event or activity has been changed from its original setting to a new one as part of a rescheduling.
-
D.
previousVenue
chosen
Indicates that one venue was used or occupied before another in a sequence of venues.
-
E.
replacedVenueLocation
Indicates that one venue location has been superseded or taken over by another venue 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a198e24881909cc292e420269a8c |
completed | May 3, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.