Triple
T38591841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brood of Nozdormu |
E932471
|
entity |
| Predicate | reputationContent |
P191459
|
FINISHED |
| Object | Temple of Ahn'Qiraj raid |
—
|
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: Temple of Ahn'Qiraj raid | Statement: [Brood of Nozdormu, reputationContent, Temple of Ahn'Qiraj raid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reputationContent Context triple: [Brood of Nozdormu, reputationContent, Temple of Ahn'Qiraj raid]
-
A.
reputationHub
Indicates a central entity that aggregates, manages, or influences the reputations of multiple other entities.
-
B.
reputationUsedFor
Indicates that an entity’s reputation is leveraged or applied for a particular purpose, function, or outcome.
-
C.
reputationBuiltFor
Indicates that one entity has established or developed a reputation specifically for or in relation to another entity.
-
D.
reputationInSources
Indicates that an entity has a certain reputation or standing as reflected or reported in various information sources.
-
E.
reputationShift
Indicates a change in how an entity is perceived or regarded by others, typically reflecting an improvement or decline in its reputation over 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.