Triple
T29746866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Hakodate |
E752777
|
entity |
| Predicate | hasPanoramaDirection |
P29603
|
FINISHED |
| Object | view toward Hakodate city |
—
|
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: view toward Hakodate city | Statement: [Mount Hakodate, hasPanoramaDirection, view toward Hakodate city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPanoramaDirection Context triple: [Mount Hakodate, hasPanoramaDirection, view toward Hakodate city]
-
A.
hasPanoramicView
chosen
Indicates that something offers a wide, unobstructed view over a broad surrounding area.
-
B.
hasPanoramaArea
Indicates that something includes or is associated with a designated area intended for panoramic viewing or wide-angle observation.
-
C.
hasPanoramaTechnique
Indicates that a subject employs or is associated with a specific panorama creation or capture technique.
-
D.
hasPanControl
Indicates that an entity has the ability to control the horizontal movement (panning) of another entity, such as a camera or view.
-
E.
hasSummitPanorama
Indicates that a summit location offers a panoramic view or image captured from its highest point.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: April 28, 2026, 7:51 p.m.