Triple
T37539206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sethekk Halls |
E933282
|
entity |
| Predicate | originalHeroicLockout |
P205962
|
FINISHED |
| Object | daily |
—
|
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: daily | Statement: [Sethekk Halls, originalHeroicLockout, daily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalHeroicLockout Context triple: [Sethekk Halls, originalHeroicLockout, daily]
-
A.
heroicLockout
Indicates a situation where an entity is prevented or restricted from accessing heroic-level content, activities, or opportunities, typically due to prior participation or imposed limits.
-
B.
heroicRequiresKey
Indicates that performing the heroic action or accessing the heroic mode is contingent on possessing a specific key.
-
C.
nativeHero
Indicates that an entity is regarded as a heroic figure originating from or strongly associated with a particular place or community.
-
D.
hasHeroicFortress
Indicates that an entity possesses or is associated with a fortress characterized by heroic qualities, status, or significance.
-
E.
lootLevelOriginalHeroic
Indicates the original heroic difficulty loot level associated with an entity or encounter.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.