Triple
T1403982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regular Northwest Face |
E31647
|
entity |
| Predicate | guidebookArea |
P27618
|
FINISHED |
| Object | Yosemite Valley big walls |
—
|
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: Yosemite Valley big walls | Statement: [Regular Northwest Face, guidebookArea, Yosemite Valley big walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidebookArea Context triple: [Regular Northwest Face, guidebookArea, Yosemite Valley big walls]
-
A.
navigationArea
Indicates that a specified region or space is designated for movement, routing, or pathfinding within an environment.
-
B.
hasLandmarkArea
Indicates that a specified area is designated as the landmark area associated with a particular entity or location.
-
C.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
-
D.
tourAccess
Indicates that an entity is permitted to participate in, enter, or make use of a specific tour.
-
E.
touristGatewayTo
Indicates a relationship where one place serves as the primary access point or entry hub for tourists visiting another place.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3a0330c8190b22452d29c79fcf4 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c11067b48190bca6ef3ac1475c20 |
completed | March 1, 2026, 10:43 p.m. |
Created at: March 1, 2026, 7:59 p.m.