Triple
T37553441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gromgol Base Camp |
E933640
|
entity |
| Predicate | providesQuestsForLevelRange |
P101767
|
FINISHED |
| Object | 30-40 |
—
|
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: 30-40 | Statement: [Gromgol Base Camp, providesQuestsForLevelRange, 30-40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesQuestsForLevelRange Context triple: [Gromgol Base Camp, providesQuestsForLevelRange, 30-40]
-
A.
hasQuestGivers
Indicates that certain entities serve as sources or providers of quests or missions for other entities.
-
B.
questlineAvailableIn
Indicates that a particular questline can be accessed or played within a specified game, mode, or context.
-
C.
combatLevelRange
Indicates the range of combat levels within which two entities can validly or effectively engage in combat with each other.
-
D.
questGiverIn
Indicates that an entity serves as the quest giver within a specified quest, location, or context.
-
E.
addsQuest
chosen
Indicates that one entity assigns or introduces a quest to another entity or into a 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_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 3, 2026, 4:17 p.m.