Triple
T38589699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Razorgore the Untamed |
E932424
|
entity |
| Predicate | isKillRequirementFor |
P191236
|
FINISHED |
| Object | progression in Blackwing Lair |
—
|
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: progression in Blackwing Lair | Statement: [Razorgore the Untamed, isKillRequirementFor, progression in Blackwing Lair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKillRequirementFor Context triple: [Razorgore the Untamed, isKillRequirementFor, progression in Blackwing Lair]
-
A.
isKilledTo
Indicates that one entity is killed as a consequence or objective of an action performed by another entity.
-
B.
canKill
Indicates that one entity has the ability or potential to cause the death of another entity.
-
C.
killsOrIsKilledBy
Indicates that one entity causes the death of the other or is itself killed by that entity, capturing a mutual or directional lethal relationship between them.
-
D.
hasKillerType
Indicates a relationship where an entity is associated with a specific type or category of killer.
-
E.
hasKiller
Indicates that one entity is the killer or cause of death of another entity.
- F. None of above. chosen
Provenance (4 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.