Triple
T28107259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull Ring modern layout |
E710396
|
entity |
| Predicate | returnedToF1Calendar |
P109357
|
FINISHED |
| Object | 2014 Austrian Grand Prix |
—
|
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: 2014 Austrian Grand Prix | Statement: [Red Bull Ring modern layout, returnedToF1Calendar, 2014 Austrian Grand Prix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToF1Calendar Context triple: [Red Bull Ring modern layout, returnedToF1Calendar, 2014 Austrian Grand Prix]
-
A.
returnedGrandPrix
chosen
Indicates that an entity has come back to participate in or host a Grand Prix event after a period of absence.
-
B.
returnedToFootball
Indicates that an entity resumed participating in football after having previously stopped or taken a break.
-
C.
returnedToCompetition
Indicates that an entity resumed participating in a competition after having previously stopped or been absent.
-
D.
returnedToTour
Indicates that an entity resumed or went back to participating in a tour after having left or paused it.
-
E.
enteredFormulaOne
Indicates that an entity began competing in Formula One racing, marking its entry into the Formula One championship.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 9:09 p.m.