Triple
T38591558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruins of Ahn'Qiraj |
E932464
|
entity |
| Predicate | primaryLoreFaction |
P167547
|
FINISHED |
| Object | Qiraji Empire |
E2277610
|
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: Qiraji Empire | Statement: [Ruins of Ahn'Qiraj, primaryLoreFaction, Qiraji Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLoreFaction Context triple: [Ruins of Ahn'Qiraj, primaryLoreFaction, Qiraji Empire]
-
A.
ownerFactionLore
Indicates that a faction holds ownership or control over the subject within the context of the lore or narrative.
-
B.
factionLore
Indicates a relationship where detailed background information or narrative history is provided about a specific faction.
-
C.
gameFaction
chosen
Indicates that an entity belongs to, is aligned with, or is a member of a particular faction within a game.
-
D.
factionOrigin
Indicates that one entity is the originating source, founding group, or initial base from which a particular faction arises or is formed.
-
E.
historicalFaction
Indicates that an entity was a member of, associated with, or part of a particular faction or side in a historical context or conflict.
- 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_6a41fd5072348190bcbac7c8696df458 |
completed | June 29, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.