Triple
T37553303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Razor Hill Outskirts |
E933637
|
entity |
| Predicate | designedForPlayerLevel |
P100059
|
FINISHED |
| Object | approximately 5–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: approximately 5–10 | Statement: [Razor Hill Outskirts, designedForPlayerLevel, approximately 5–10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForPlayerLevel Context triple: [Razor Hill Outskirts, designedForPlayerLevel, approximately 5–10]
-
A.
intendedPlayerLevel
chosen
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
B.
designedForLevelCap
Indicates that something is specifically created or configured to be suitable for use at a particular maximum level or level cap.
-
C.
usedForLevelOfPlay
Indicates that something is intended or suitable for a particular level or standard of play.
-
D.
levelRequirement
Indicates that one entity specifies the minimum level or threshold another entity must meet in order for an action, access, or condition to be valid.
-
E.
requiresSkillLevel
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:17 p.m.