Triple
T1770619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Masque of the Red Death |
E38865
|
entity |
| Predicate | climax |
P10235
|
FINISHED |
| Object | revelation of the Red Death at the masquerade |
—
|
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: revelation of the Red Death at the masquerade | Statement: [The Masque of the Red Death, climax, revelation of the Red Death at the masquerade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climax Context triple: [The Masque of the Red Death, climax, revelation of the Red Death at the masquerade]
-
A.
crest
chosen
Indicates reaching the highest point or peak of something, such as a wave, hill, or trend, before it begins to decline.
-
B.
epicenter
Indicates the central point or focal location from which an event, influence, or effect originates or is most intensely experienced.
-
C.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
-
D.
reachesSummit
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
-
E.
crestFeature
Indicates that an entity possesses a notable crest-related characteristic or structural feature.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.