Triple
T3624771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steffen Glacier |
E76809
|
entity |
| Predicate | hasAccessDifficulty |
P11058
|
FINISHED |
| Object | hard to access due to remoteness |
—
|
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: hard to access due to remoteness | Statement: [Steffen Glacier, hasAccessDifficulty, hard to access due to remoteness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessDifficulty Context triple: [Steffen Glacier, hasAccessDifficulty, hard to access due to remoteness]
-
A.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
B.
hasAccessTowards
Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
-
C.
hasDisabledAccess
Indicates that an entity provides facilities, features, or accommodations that make it accessible to people with disabilities.
-
D.
isDifficultToAccessBecauseOf
chosen
Indicates that something is hard to reach, obtain, or use due to a specified obstacle, condition, or circumstance.
-
E.
hasMeasurementDifficulty
Indicates that performing a measurement on something is challenging or problematic in some way.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2d9845c8190ad65b2471000dfa0 |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.