Triple
T7390691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sickness Unto Death |
E170488
|
entity |
| Predicate | dividesDespairInto |
P889
|
FINISHED |
| Object | despair of weakness |
—
|
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: despair of weakness | Statement: [The Sickness Unto Death, dividesDespairInto, despair of weakness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dividesDespairInto Context triple: [The Sickness Unto Death, dividesDespairInto, despair of weakness]
-
A.
downfall
Indicates the process or event by which an entity experiences a significant decline, ruin, or loss of power, status, or success.
-
B.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
C.
isDividedFrom
Indicates that one entity is separated or partitioned from another, typically by a boundary, barrier, or dividing line.
-
D.
division
chosen
Indicates a relationship where one entity is separated or partitioned into parts, groups, or sections based on some criterion or operation.
-
E.
divisionSince
Indicates that one entity has been divided or split from another starting at a specific point in time.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2216a5c8190a933b24fda4530d8 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.