Triple
T20217200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finsteraarhornhütte |
E495157
|
entity |
| Predicate | requiresAccessBy |
P39227
|
FINISHED |
| Object | glacier travel |
—
|
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: glacier travel | Statement: [Finsteraarhornhütte, requiresAccessBy, glacier travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresAccessBy Context triple: [Finsteraarhornhütte, requiresAccessBy, glacier travel]
-
A.
assuredAccessRequirement
Indicates that one entity requires guaranteed, reliable access to another entity, resource, or service as a condition or constraint.
-
B.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
C.
hasAccessBy
Indicates that one entity is permitted to access, use, or interact with another entity, typically under specified permissions or conditions.
-
D.
requiresPermitFor
Indicates that one entity must obtain formal permission or authorization before performing an action involving another entity.
-
E.
requiresForAccession
chosen
Indicates that one entity must be obtained, completed, or satisfied before another entity can be accessed, entered, or formally joined.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66eda2f188190adf39d895e8b99f2 |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.