Triple
T13914248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bystra |
E334576
|
entity |
| Predicate | hasTypicalAccess |
P112265
|
FINISHED |
| Object | marked hiking trails |
—
|
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: marked hiking trails | Statement: [Bystra, hasTypicalAccess, marked hiking trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAccess Context triple: [Bystra, hasTypicalAccess, marked hiking trails]
-
A.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
B.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
C.
hasAccessTowards
Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
-
D.
hasAccessModel
Indicates that one entity is permitted to use, interact with, or retrieve a particular model controlled by another entity or system.
-
E.
hasAccessMode
Indicates the type or method of access that one entity is permitted to use with respect to 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27245c648190b2946845ce0fdbf8 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:16 p.m.