Triple
T37591769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zul'Gurub |
E935276
|
entity |
| Predicate | releasePatchName |
P99621
|
FINISHED |
| Object | Rise of the Blood God |
—
|
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: Rise of the Blood God | Statement: [Zul'Gurub, releasePatchName, Rise of the Blood God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasePatchName Context triple: [Zul'Gurub, releasePatchName, Rise of the Blood God]
-
A.
releaseName
Indicates that an entity is identified or labeled by a specific release name (e.g., version or edition title).
-
B.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
-
C.
patchName
chosen
Indicates the specific name or identifier assigned to a software patch applied to an entity.
-
D.
releaseChannel
Indicates the distribution pathway or medium through which something (such as a product, update, or content) is made available or delivered to its recipients.
-
E.
releaseGeneration
Indicates that one entity causes or initiates the production or emission of another entity or resource.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:18 p.m.