Triple
T37507286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calcis |
E932128
|
entity |
| Predicate | playerLevelRangeContext |
P100059
|
FINISHED |
| Object | max-level characters |
—
|
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: max-level characters | Statement: [Calcis, playerLevelRangeContext, max-level characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerLevelRangeContext Context triple: [Calcis, playerLevelRangeContext, max-level characters]
-
A.
combatLevelRange
Indicates the range of combat levels within which two entities can validly or effectively engage in combat with each other.
-
B.
yLevelRange
Indicates that one entity’s vertical position or height falls within a specified range relative to another entity or reference level.
-
C.
intendedPlayerLevel
chosen
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
D.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
E.
gearItemLevelRange
Indicates the range of item levels that a piece of gear can or does fall within.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:17 p.m.