Triple
T37539018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghostlands |
E933278
|
entity |
| Predicate | startingLevelRange |
P203098
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Ghostlands, startingLevelRange, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingLevelRange Context triple: [Ghostlands, startingLevelRange, 10]
-
A.
combatLevelRange
Indicates the range of combat levels within which two entities can validly or effectively engage in combat with each other.
-
B.
requiresLevelRange
Indicates that something is only applicable, accessible, or valid for entities whose level falls within a specified minimum-to-maximum range.
-
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.
zoneLevelRangeAtLaunch
Indicates the range of zone levels that apply at the moment something is launched or begins.
-
E.
reintroducedLevelRange
Indicates that an entity has been reintroduced within a specified range or interval of levels.
- F. None of above. chosen
Provenance (4 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a011ee3507081908b42de4278ae0b83 |
completed | May 11, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_6a011e874420819091cac3f08e8aa3f9 |
completed | May 11, 2026, 12:10 a.m. |
| PDg | Predicate description generation | batch_6a011ee2a6408190b3b2763d01bac623 |
completed | May 11, 2026, 12:12 a.m. |
Created at: May 3, 2026, 4:17 p.m.