Triple
T12077817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabletop Mountain (Adirondacks) |
E287596
|
entity |
| Predicate | hasSummitViewsVia |
P103083
|
FINISHED |
| Object | short side paths |
—
|
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: short side paths | Statement: [Tabletop Mountain (Adirondacks), hasSummitViewsVia, short side paths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitViewsVia Context triple: [Tabletop Mountain (Adirondacks), hasSummitViewsVia, short side paths]
-
A.
hasSummitViewsOf
Indicates that from the summit of one location, there are views overlooking or directed toward another location.
-
B.
hasSummitPanorama
Indicates that a summit location offers a panoramic view or image captured from its highest point.
-
C.
hasSummitIn
Indicates that an entity (such as a mountain or organization) has its summit or peak located within a specified place or region.
-
D.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
E.
hasSummitUse
Indicates that something is designated for use specifically at or on a summit (e.g., the top of a mountain or peak).
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bf4f508190842927e7e0642235 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d91006e14081909838412df082f794 |
completed | April 10, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:48 p.m.