Triple
T14620184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pelion Hut |
E343195
|
entity |
| Predicate | hasLevelOfDifficultyToReach |
P24163
|
FINISHED |
| Object | moderate |
—
|
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: moderate | Statement: [Pelion Hut, hasLevelOfDifficultyToReach, moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelOfDifficultyToReach Context triple: [Pelion Hut, hasLevelOfDifficultyToReach, moderate]
-
A.
hasDifficultyContext
Indicates that something’s difficulty is defined, interpreted, or constrained within a particular situational or contextual framework.
-
B.
requiresSkillLevel
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
-
C.
intendedPlayerLevel
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
D.
mayBeChallengedBy
Indicates that one entity is allowed or able to be opposed, questioned, or contested by another entity.
-
E.
hasTrailDifficulty
chosen
Indicates the level of challenge or effort required to traverse a particular trail or route.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb46550e48190af45f426f02579bb |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.