Triple
T30594525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Works trailhead |
E778748
|
entity |
| Predicate | accessesPeakRegion |
P178334
|
FINISHED |
| Object | Mount Marcy area |
—
|
NE NERFINISHED |
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: Mount Marcy area | Statement: [Upper Works trailhead, accessesPeakRegion, Mount Marcy area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesPeakRegion Context triple: [Upper Works trailhead, accessesPeakRegion, Mount Marcy area]
-
A.
highestPeakAccessed
Indicates that one entity has reached or visited the tallest peak associated with another entity or within a specified context.
-
B.
hasPeakAssociated
Indicates that one entity is linked or related to a specific peak (such as a summit or maximum point) associated with it.
-
C.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
D.
highestPeakAccessible
Indicates that one location is the tallest peak that can be reached or accessed from another specified location or by a specified agent.
-
E.
hasPeakAround
Indicates that something exhibits a maximum value, intensity, or prominence in the vicinity of a specified point, range, or condition.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 29, 2026, 8:24 p.m.