Triple
T4701877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waimea, Hawaii County, Hawaii |
E104291
|
entity |
| Predicate | hasScenicViews |
P9193
|
FINISHED |
| Object | nearby volcanic peaks |
—
|
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: nearby volcanic peaks | Statement: [Waimea, Hawaii County, Hawaii, hasScenicViews, nearby volcanic peaks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScenicViews Context triple: [Waimea, Hawaii County, Hawaii, hasScenicViews, nearby volcanic peaks]
-
A.
hasScenicViewOf
chosen
Indicates that one entity offers a visually appealing or picturesque view of another entity.
-
B.
hasScenicSections
Indicates that a route, path, or area contains segments that are visually attractive or offer notable scenic views.
-
C.
hasScenicValue
Indicates that something possesses notable aesthetic or visual appeal, often due to its natural beauty or pleasing surroundings.
-
D.
isPartOfScenicVista
Indicates that something is included within, or contributes to, a larger scenic vista or panoramic view.
-
E.
hasScenicDrive
Indicates that one entity offers or features a visually appealing or picturesque driving route associated with it.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.