Triple
T38584404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellfire Ramparts |
E932313
|
entity |
| Predicate | recommendedLevelRangeOriginal |
P190556
|
FINISHED |
| Object | 60-62 |
—
|
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: 60-62 | Statement: [Hellfire Ramparts, recommendedLevelRangeOriginal, 60-62]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedLevelRangeOriginal Context triple: [Hellfire Ramparts, recommendedLevelRangeOriginal, 60-62]
-
A.
recommendedLevelAtLaunch
Indicates the level that is advised or expected for an entity at the moment it is first introduced or made available.
-
B.
intendedPlayerLevel
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
C.
representedAgeLevel
Indicates that one entity corresponds to, or is categorized under, a particular age level or age group.
-
D.
eligibilityGradeLevel
Indicates the grade level or range of grade levels for which an entity is considered eligible or appropriate.
-
E.
levelRangeClassic
chosen
Indicates that something is associated with, valid for, or constrained to a specific range of levels in a classic or original-version context.
- 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_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.