Triple
T38584580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Underbog |
E932317
|
entity |
| Predicate | factionLevelRange |
P193984
|
FINISHED |
| Object | 60-70 |
—
|
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-70 | Statement: [The Underbog, factionLevelRange, 60-70]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionLevelRange Context triple: [The Underbog, factionLevelRange, 60-70]
-
A.
combatLevelRange
Indicates the range of combat levels within which two entities can validly or effectively engage in combat with each other.
-
B.
zoneLevelRange
Indicates the range of zone levels within which a given condition, rule, or classification applies.
-
C.
difficultyClassRange
Indicates the range of difficulty classes within which an action, task, or challenge is considered to fall.
-
D.
factionID
Indicates that an entity is associated with, or belongs to, a particular faction identified by a specific ID.
-
E.
levelRangeClassic
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. 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: May 3, 2026, 4:32 p.m.