Triple
T38590103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elementium Reinforced Bulwark |
E932433
|
entity |
| Predicate | heroicSourceDifficulty |
P78451
|
FINISHED |
| Object | 10-player heroic |
—
|
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: 10-player heroic | Statement: [Elementium Reinforced Bulwark, heroicSourceDifficulty, 10-player heroic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroicSourceDifficulty Context triple: [Elementium Reinforced Bulwark, heroicSourceDifficulty, 10-player heroic]
-
A.
heroicLevel
Indicates the degree or extent to which an entity exhibits heroism or heroic qualities.
-
B.
difficultySource
chosen
Indicates that one entity is the cause, origin, or contributing factor to the difficulty or challenge experienced in relation to another entity or situation.
-
C.
hasDifficultyEffect
Indicates that one entity causes a change in the difficulty level or challenge associated with another entity or activity.
-
D.
heroicStatus
Indicates that an entity possesses qualities or recognition associated with being a hero, such as bravery, selflessness, or notable heroic deeds.
-
E.
difficultyRole
Indicates the level or type of challenge associated with performing a particular role or function.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:32 p.m.