Triple
T30633128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Seven Rings for the Dwarf-lords |
E779762
|
entity |
| Predicate | failedEffect |
P159544
|
FINISHED |
| Object | did not turn Dwarves into wraiths |
—
|
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: did not turn Dwarves into wraiths | Statement: [The Seven Rings for the Dwarf-lords, failedEffect, did not turn Dwarves into wraiths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failedEffect Context triple: [The Seven Rings for the Dwarf-lords, failedEffect, did not turn Dwarves into wraiths]
-
A.
failureEffect
chosen
Indicates the resulting condition, consequence, or outcome that occurs when a failure happens.
-
B.
failed
Indicates that an attempted action or process did not succeed in achieving its intended outcome.
-
C.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
D.
failureEvent
Indicates that an action, process, or system has not achieved its intended outcome, resulting in a failure occurrence.
-
E.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a1ee6348190a316b92bccd14826 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:28 p.m.