Triple
T31946465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yharnam |
E815663
|
entity |
| Predicate | plaguedBy |
P169604
|
FINISHED |
| Object | beastly scourge |
—
|
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: beastly scourge | Statement: [Yharnam, plaguedBy, beastly scourge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plaguedBy Context triple: [Yharnam, plaguedBy, beastly scourge]
-
A.
blightedBy
chosen
Indicates that one entity is negatively affected, damaged, or ruined by another entity or factor.
-
B.
wrongedBy
Indicates that one entity has been harmed, treated unjustly, or suffered a grievance as a result of another entity's actions.
-
C.
correctsAberration
Indicates that one entity counteracts, fixes, or compensates for an error, flaw, or deviation present in another entity.
-
D.
blamedOn
Indicates that responsibility or fault for something is assigned to a particular entity.
-
E.
corrupts
Indicates that one entity causes another entity, system, or process to become morally, functionally, or structurally degraded or impaired.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b27a431c81909c5de3770a594b88 |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:06 a.m.