Triple
T19134826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limbo |
E468408
|
entity |
| Predicate | tormentType |
P117279
|
FINISHED |
| Object | absence of physical torment |
—
|
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: absence of physical torment | Statement: [Limbo, tormentType, absence of physical torment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tormentType Context triple: [Limbo, tormentType, absence of physical torment]
-
A.
corruptingForceType
Indicates a type or category of influence that causes moral, ethical, or structural degradation in the affected entity.
-
B.
typeOfEvil
chosen
Indicates that one entity is classified as a specific kind or category of evil in relation to another.
-
C.
useOfTorture
Indicates the intentional infliction or use of torture by one entity upon another, typically to punish, coerce, intimidate, or extract information.
-
D.
IntimidatorType
Indicates that one entity acts as a source or type of intimidation toward another entity.
-
E.
torturedAt
Indicates that an entity was subjected to torture at a specific location or facility.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ec4c848190af450bf5bf8db5e7 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.