Triple
T28990964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Austrian Grand Prix |
E736023
|
entity |
| Predicate | spectatorIncidentsReported |
P80733
|
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: [2022 Austrian Grand Prix, spectatorIncidentsReported, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectatorIncidentsReported Context triple: [2022 Austrian Grand Prix, spectatorIncidentsReported, yes]
-
A.
fanIncidents
chosen
Indicates incidents or problematic events involving fans in relation to a particular subject, such as a team, event, or performance.
-
B.
spectatorSafetyFocus
Indicates that the primary concern or emphasis of an action, policy, or design is on ensuring the safety and protection of spectators.
-
C.
spectatorAppeal
Indicates that an action, event, or entity is appealing, entertaining, or attractive to spectators or an audience.
-
D.
reportsEventsAt
Indicates that one entity provides information or reports about events occurring at a specific location or time.
-
E.
spectatorsFrom
Indicates that one or more spectators originate from, are associated with, or come to an event from a particular place or source.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7d3b5c8190937aaddff2879989 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:25 a.m.