Triple
T1781768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pit and the Pendulum |
E39304
|
entity |
| Predicate | climaxFeature |
P7326
|
FINISHED |
| Object | rescue at the brink of death |
—
|
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: rescue at the brink of death | Statement: [The Pit and the Pendulum, climaxFeature, rescue at the brink of death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climaxFeature Context triple: [The Pit and the Pendulum, climaxFeature, rescue at the brink of death]
-
A.
crestFeature
Indicates that an entity possesses a notable crest-related characteristic or structural feature.
-
B.
crest
Indicates reaching the highest point or peak of something, such as a wave, hill, or trend, before it begins to decline.
-
C.
specialFeature
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
-
D.
keyFeature
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
E.
notableScene
chosen
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.