Triple
T7390693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sickness Unto Death |
E170488
|
entity |
| Predicate | definesSelfAs |
P4296
|
FINISHED |
| Object | a relation that relates itself to itself |
—
|
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: a relation that relates itself to itself | Statement: [The Sickness Unto Death, definesSelfAs, a relation that relates itself to itself]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesSelfAs Context triple: [The Sickness Unto Death, definesSelfAs, a relation that relates itself to itself]
-
A.
usedAsSelfDesignation
Indicates that an entity is used by a person or group as a term to refer to or identify themselves.
-
B.
definesSystemAs
Indicates that one entity explicitly specifies or establishes another entity as the system to be used, referenced, or treated as authoritative.
-
C.
calledHimself
Indicates that a person referred to or identified himself using a particular name, title, or description.
-
D.
considersItself
Indicates that an entity regards or perceives itself in a particular way, role, or state.
-
E.
selfIdentification
chosen
Indicates that an entity defines or declares its own identity, attributes, or classification about itself.
- 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.