Triple
T37554451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydraxian Waterlords |
E933660
|
entity |
| Predicate | questContentLevelRange |
P100059
|
FINISHED |
| Object | 60 |
—
|
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 | Statement: [Hydraxian Waterlords, questContentLevelRange, 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questContentLevelRange Context triple: [Hydraxian Waterlords, questContentLevelRange, 60]
-
A.
combatLevelRange
Indicates the range of combat levels within which two entities can validly or effectively engage in combat with each other.
-
B.
intendedPlayerLevel
chosen
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
C.
entranceZoneLevelRange
Indicates the range of zone or area levels that are appropriate or allowed for entering a particular location or instance.
-
D.
levelRequirement
Indicates that one entity specifies the minimum level or threshold another entity must meet in order for an action, access, or condition to be valid.
-
E.
gearItemLevelRange
Indicates the range of item levels that a piece of gear can or does fall within.
- 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_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:17 p.m.