Triple
T38591959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silithid |
E932473
|
entity |
| Predicate | notableRaidAssociation |
P100069
|
FINISHED |
| Object | Temple of Ahn'Qiraj |
E932464
|
NE 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 | Statement: [Silithid, notableRaidAssociation, Temple of Ahn'Qiraj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRaidAssociation Context triple: [Silithid, notableRaidAssociation, Temple of Ahn'Qiraj]
-
A.
associatedRaid
chosen
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
B.
notableBoss
Indicates that one entity is a boss or superior of another in a way that is particularly prominent, distinguished, or noteworthy.
-
C.
majorRaid
Indicates a large-scale, coordinated attack or incursion carried out against a target.
-
D.
raidBossIn
Indicates that an entity serves as or is designated as the raid boss within a specified raid, instance, or location.
-
E.
keyItemRaid
Indicates a raid or mission whose primary objective is to obtain or secure a key item.
- F. None of above.
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_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a42341c2f6c8190b30eb967b8de17d3 |
completed | June 29, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.