Triple
T37554234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bindings of the Windseeker |
E933655
|
entity |
| Predicate | itemLevel |
P100071
|
FINISHED |
| Object | legendary quest component level (classic) |
—
|
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: legendary quest component level (classic) | Statement: [Bindings of the Windseeker, itemLevel, legendary quest component level (classic)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: itemLevel Context triple: [Bindings of the Windseeker, itemLevel, legendary quest component level (classic)]
-
A.
gearItemLevelRange
chosen
Indicates the range of item levels that a piece of gear can or does fall within.
-
B.
typicalEquipmentLevel
Indicates the usual or standard amount or quality of equipment associated with an entity or situation.
-
C.
intendedPlayerLevel
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
D.
weaponTier
Indicates the relative quality or strength level assigned to a weapon within a ranked or graded system.
-
E.
spellLevel
Indicates the level or rank assigned to a spell within a spellcasting or magic system.
- 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_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.