Triple
T23823251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Conte Canyon |
E589292
|
entity |
| Predicate | requiresAccessMode |
P6865
|
FINISHED |
| Object | foot 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: foot travel | Statement: [Le Conte Canyon, requiresAccessMode, foot travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresAccessMode Context triple: [Le Conte Canyon, requiresAccessMode, foot travel]
-
A.
hasAccessMode
chosen
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
-
B.
assuredAccessRequirement
Indicates that one entity requires guaranteed, reliable access to another entity, resource, or service as a condition or constraint.
-
C.
accessMode
Indicates the manner or method by which an entity can be accessed, used, or interacted with.
-
D.
requiresPrivileges
Indicates that performing the referenced action or accessing the referenced resource is contingent on the actor having specific privileges or permissions.
-
E.
requiresForFullAuthority
Indicates that possessing or satisfying the referenced element is a necessary condition for obtaining full authority.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7b12520819086daf8c284732e0f |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:59 p.m.