Triple
T6611773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Schumacher |
E149252
|
entity |
| Predicate | sufferedAccident |
P32122
|
FINISHED |
| Object | skiing accident in December 2013 |
—
|
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: skiing accident in December 2013 | Statement: [Michael Schumacher, sufferedAccident, skiing accident in December 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedAccident Context triple: [Michael Schumacher, sufferedAccident, skiing accident in December 2013]
-
A.
involvedInAccident
chosen
Indicates that an entity participated in, was affected by, or was otherwise a party to a specific accident or collision event.
-
B.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
C.
accident
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
-
D.
hasInjuredPerson
Indicates that an entity has a person who has been harmed or injured associated with it.
-
E.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cf3796d08190a26e988386089447 |
completed | March 27, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69c6acfed25481909cac74c84a9fe088 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:57 p.m.