Triple
T34882458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Dave Osborne |
E1006051
|
entity |
| Predicate | typicalOutcomeOfStunts |
P59870
|
FINISHED |
| Object | catastrophic failure |
—
|
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: catastrophic failure | Statement: [Super Dave Osborne, typicalOutcomeOfStunts, catastrophic failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOutcomeOfStunts Context triple: [Super Dave Osborne, typicalOutcomeOfStunts, catastrophic failure]
-
A.
safetyOutcome
Indicates the resulting condition or consequence related to safety that arises from an action, event, or situation.
-
B.
resultOfFall
Indicates that something exists or occurs as a consequence or outcome of a fall event.
-
C.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
D.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
E.
commonOutcomeFor
Indicates that multiple entities share the same resulting state, effect, or consequence.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.