Triple
T35293184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloudrest |
E1019284
|
entity |
| Predicate | recommendedLevel |
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: [Cloudrest, recommendedLevel, max level characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedLevel Context triple: [Cloudrest, recommendedLevel, max level characters]
-
A.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
B.
qualificationLevel
Indicates the degree or rank of competence, certification, or formal credentials required for or possessed in relation to something.
-
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.
minimumLevel
Indicates that one entity specifies the lowest allowable or required level, degree, or threshold at which another entity, condition, or action becomes valid or applicable.
-
E.
recruitedLevel
Indicates that one entity has been recruited or enlisted by another at a specified level, rank, or stage within some process or organization.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.