Triple
T37553746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackrock Depths |
E933645
|
entity |
| Predicate | hasKeyMechanic |
P187880
|
FINISHED |
| Object | Shadowforge Key |
—
|
NE NERFINISHED |
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: Shadowforge Key | Statement: [Blackrock Depths, hasKeyMechanic, Shadowforge Key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyMechanic Context triple: [Blackrock Depths, hasKeyMechanic, Shadowforge Key]
-
A.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
B.
hasMechanicalFeature
Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
-
C.
hasTriggerMechanism
Indicates that an entity possesses or is equipped with a specific mechanism used to initiate or activate an action or process.
-
D.
hasSignatureMechanic
Indicates that an entity (such as a game, character, or system) possesses a distinctive, defining mechanic or feature that is uniquely characteristic of it.
-
E.
keyMechanic
chosen
Indicates that the referenced element functions as a central or essential gameplay mechanic within a system or experience.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:17 p.m.