Triple
T35012230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auridon |
E1009962
|
entity |
| Predicate | levelRangeInESO |
P100055
|
FINISHED |
| Object | starter to early-game |
—
|
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: starter to early-game | Statement: [Auridon, levelRangeInESO, starter to early-game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelRangeInESO Context triple: [Auridon, levelRangeInESO, starter to early-game]
-
A.
levelIDescription
Indicates that an entity provides a textual description of its difficulty or progression level.
-
B.
yLevelRange
Indicates that one entity’s vertical position or height falls within a specified range relative to another entity or reference level.
-
C.
zoneLevelRange
chosen
Indicates the range of zone levels within which a given condition, rule, or classification applies.
-
D.
enrichmentLevelRange
Indicates the range of values within which the level or degree of enrichment is considered or specified.
-
E.
levels
Indicates that one entity adjusts, equalizes, or smooths out the height, intensity, or degree of another entity.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.