Triple
T38591564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruins of Ahn'Qiraj |
E932464
|
entity |
| Predicate | requiresEventToOpen |
P188896
|
FINISHED |
| Object | Gates of Ahn'Qiraj opening |
—
|
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: Gates of Ahn'Qiraj opening | Statement: [Ruins of Ahn'Qiraj, requiresEventToOpen, Gates of Ahn'Qiraj opening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresEventToOpen Context triple: [Ruins of Ahn'Qiraj, requiresEventToOpen, Gates of Ahn'Qiraj opening]
-
A.
eventRequirements
Indicates that certain conditions, resources, or prerequisites must be satisfied for an event to occur or be valid.
-
B.
openedForEvent
Indicates that a venue or location is made accessible and operational specifically for a particular event.
-
C.
requiresToAccess
Indicates that one entity must be obtained, satisfied, or fulfilled in order to gain access to another entity.
-
D.
openedByEvent
chosen
Indicates that something is initiated, activated, or made accessible as a direct result of a specific event.
-
E.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00c59b03dc8190870f0dd24603a1ef |
completed | May 10, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a00c5178bc88190b2a0e03f38314035 |
completed | May 10, 2026, 5:49 p.m. |
Created at: May 3, 2026, 4:32 p.m.