Triple
T37465653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Y’Shaarj, the Defiler |
E931026
|
entity |
| Predicate | remnantUsedBy |
P187968
|
FINISHED |
| Object | Garrosh Hellscream |
—
|
NE NERFINISHED |
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: Garrosh Hellscream | Statement: [Y’Shaarj, the Defiler, remnantUsedBy, Garrosh Hellscream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remnantUsedBy Context triple: [Y’Shaarj, the Defiler, remnantUsedBy, Garrosh Hellscream]
-
A.
remnantName
Indicates that an entity is identified by a name specifically associated with a remaining part, leftover, or surviving fragment of something previously whole.
-
B.
remnantType
Indicates the specific kind or category of remnant that results from or is associated with an entity or process.
-
C.
remnants
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
D.
remnantsInclude
Indicates that the remaining parts or leftovers of one entity contain or consist of another entity.
-
E.
stillUsedBy
Indicates that something continues to be used or relied upon by another entity at the present time.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.