Triple
T38644513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rise of Azshara |
E938680
|
entity |
| Predicate | includesDungeon |
P100053
|
FINISHED |
| Object | Operation: Mechagon |
E2254626
|
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: Operation: Mechagon | Statement: [Rise of Azshara, includesDungeon, Operation: Mechagon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDungeon Context triple: [Rise of Azshara, includesDungeon, Operation: Mechagon]
-
A.
hasDungeon
chosen
Indicates that one entity possesses, contains, or includes a dungeon as part of its structure, property, or domain.
-
B.
requiresDungeon
Indicates that performing the action or establishing the relationship is contingent on the presence or completion of a specific dungeon.
-
C.
dungeonType
Indicates the specific category or kind of dungeon associated with an entity or location.
-
D.
notableDungeon
Indicates that an entity is recognized as a significant or noteworthy dungeon, typically due to its importance, uniqueness, or prominence.
-
E.
majorDungeonFeature
Indicates that something serves as a primary or defining structural or thematic element of a dungeon.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4205b84ba881908ea5c4ff8becc791 |
completed | June 29, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.