Triple
T27424627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grewingk Glacier |
E690446
|
entity |
| Predicate | hasTrailToViewpoint |
P93497
|
FINISHED |
| Object | Grewingk Glacier Trail |
—
|
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: Grewingk Glacier Trail | Statement: [Grewingk Glacier, hasTrailToViewpoint, Grewingk Glacier Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrailToViewpoint Context triple: [Grewingk Glacier, hasTrailToViewpoint, Grewingk Glacier Trail]
-
A.
hasTrailAccessPoint
chosen
Indicates that there is a specific access point or entrance connecting a location to a trail or pathway.
-
B.
isScenicViewpoint
Indicates that a location offers a notable, aesthetically pleasing view of the surrounding landscape.
-
C.
hasViewingPointFor
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
-
D.
hasScenicViewOf
Indicates that one entity offers a visually appealing or picturesque view of another entity.
-
E.
hasScenicViewpoints
Indicates that something includes or provides locations specifically intended for enjoying scenic or panoramic views.
- 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 27, 2026, 12:40 p.m.