Triple
T37471771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirna Scithe |
E931170
|
entity |
| Predicate | availableInDifficulty |
P188180
|
FINISHED |
| Object | Normal |
—
|
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: Normal | Statement: [Tirna Scithe, availableInDifficulty, Normal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableInDifficulty Context triple: [Tirna Scithe, availableInDifficulty, Normal]
-
A.
hasDifficultyClass
Indicates that something (such as a task, challenge, or problem) is associated with a specific level of difficulty or complexity.
-
B.
raidDifficultyAvailability
chosen
Indicates how the availability or accessibility of a raid changes based on its selected difficulty level.
-
C.
hasDifficultyContext
Indicates that something’s difficulty is defined, interpreted, or constrained within a particular situational or contextual framework.
-
D.
difficultyClassRange
Indicates the range of difficulty classes within which an action, task, or challenge is considered to fall.
-
E.
hasRecreationDifficulty
Indicates the level of challenge or effort required to engage in a particular recreational activity 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.