Triple
T20210208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dementor’s Kiss |
E493468
|
entity |
| Predicate | unofficialDescription |
P59393
|
FINISHED |
| Object | fate worse than 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: fate worse than death | Statement: [Dementor’s Kiss, unofficialDescription, fate worse than death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unofficialDescription Context triple: [Dementor’s Kiss, unofficialDescription, fate worse than death]
-
A.
socialDescription
Indicates that one entity provides a textual or narrative description of another entity in a social or interpersonal context.
-
B.
officiallyDescribedAs
Indicates that an entity is formally characterized or defined using a specific description in an official or authoritative context.
-
C.
typicalOnsetDescription
Indicates the usual or characteristic way in which a condition, event, or process begins or first presents itself.
-
D.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
E.
popularDescription
chosen
Indicates that an entity has a commonly used or widely recognized descriptive text or label associated with it.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed4706c81908a5e4a3023a9c22f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.