Triple
T35753213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Grand Prix |
E1033370
|
entity |
| Predicate | hasHostedDryRaces |
P195562
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [German Grand Prix, hasHostedDryRaces, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostedDryRaces Context triple: [German Grand Prix, hasHostedDryRaces, yes]
-
A.
hasHostedWetRaces
Indicates that the subject has previously hosted races that took place under wet conditions (e.g., rain or a wet track).
-
B.
hasHostedSport
Indicates that a place or organization has served as the venue or organizer for one or more sporting events.
-
C.
hasHostedVenue
Indicates that a particular venue has served as the location for hosting a specific event or activity.
-
D.
hasHeldRacesInCity
Indicates that an entity has organized or conducted races that took place within a particular city.
-
E.
heldRacesIn
Indicates that an entity organized or hosted races at a particular location or event.
- F. None of above. chosen
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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69fdd922d73c81908ad3faade247ec16 |
completed | May 8, 2026, 12:37 p.m. |
Created at: May 3, 2026, 4:06 p.m.