Triple
T37592239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loatheb |
E935287
|
entity |
| Predicate | tierOfContent |
P59179
|
FINISHED |
| Object | level 60 raid content |
—
|
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: level 60 raid content | Statement: [Loatheb, tierOfContent, level 60 raid content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierOfContent Context triple: [Loatheb, tierOfContent, level 60 raid content]
-
A.
contentLevel
Indicates the degree or intensity of substance, complexity, or richness present in the associated content.
-
B.
tiered
Indicates that something is organized into multiple hierarchical levels or layers, often with differing degrees of priority, access, or benefit.
-
C.
tierOfGame
Indicates the classification level or rank assigned to a game within a hierarchical system.
-
D.
curationLevel
Indicates the degree or extent to which something has been deliberately selected, organized, or refined by a curator or curatorial process.
-
E.
partOfTier
chosen
Indicates that one entity belongs to, is included within, or forms a component of a specified tier or level in a hierarchical structure.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.