Triple
T26855099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snowcrest Range |
E676168
|
entity |
| Predicate | humanAccessLevel |
P161535
|
FINISHED |
| Object | limited road access |
—
|
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: limited road access | Statement: [Snowcrest Range, humanAccessLevel, limited road access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanAccessLevel Context triple: [Snowcrest Range, humanAccessLevel, limited road access]
-
A.
authorizationLevel
Indicates the degree or tier of access rights or permissions granted to an entity within a system or context.
-
B.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
-
C.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
D.
hasAccessTier
Indicates that one entity is assigned or associated with a specific level or tier of access permissions to another entity or resource.
-
E.
hasAccessTowards
Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
- F. None of above. chosen
Provenance (4 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61b95f7f881909372cf7d15db1949 |
completed | May 2, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6142a0b988190b404d078f73c3cb9 |
completed | May 2, 2026, 3:11 p.m. |
Created at: April 27, 2026, 5:20 a.m.