Triple
T35752430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Austrian Grand Prix |
E1033351
|
entity |
| Predicate | teamInvolvedInNotableIncident |
P48917
|
FINISHED |
| Object | Mercedes |
—
|
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: Mercedes | Statement: [2016 Austrian Grand Prix, teamInvolvedInNotableIncident, Mercedes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamInvolvedInNotableIncident Context triple: [2016 Austrian Grand Prix, teamInvolvedInNotableIncident, Mercedes]
-
A.
notableIncidentType
Indicates the specific category or kind of significant event or incident associated with an entity.
-
B.
teamInNotableEvent
chosen
Indicates that a team participated in or was involved with a notable event.
-
C.
hasNotableIncident
Indicates that an entity is associated with a significant or noteworthy event, occurrence, or incident.
-
D.
bearerNotableEvent
Indicates that a bearer (such as a person or entity) is associated with a specific notable event in which they played a significant role.
-
E.
hasBeenInvolvedIn
Indicates that an entity has participated in, taken part in, or been connected to a particular event, activity, or situation.
- 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_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.