Triple
T17217234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge of Death |
E417883
|
entity |
| Predicate | penaltyForFailure |
P1841
|
FINISHED |
| Object | being cast into the Gorge of Eternal Peril |
—
|
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: being cast into the Gorge of Eternal Peril | Statement: [Bridge of Death, penaltyForFailure, being cast into the Gorge of Eternal Peril]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penaltyForFailure Context triple: [Bridge of Death, penaltyForFailure, being cast into the Gorge of Eternal Peril]
-
A.
defaultPenalty
Indicates that a standard or automatically applied penalty is imposed in the absence of a specific or overridden penalty.
-
B.
penaltyMechanism
Indicates a relationship where a rule, system, or process imposes a negative consequence or sanction in response to certain actions or conditions.
-
C.
supportsPenalty
Indicates that one entity endorses, approves of, or is in favor of a particular penalty being applied to another entity or situation.
-
D.
penaltyProvision
chosen
Indicates that a rule, contract, or law includes a clause specifying a punishment or sanction for non-compliance or violation.
-
E.
penaltySaveBy
Indicates that a penalty kick was successfully saved by a particular goalkeeper.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dda6e6c81908dd96f653cd2cba0 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.