Triple
T27864346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nihondaira |
E704314
|
entity |
| Predicate | isScenicSpotFor |
P157505
|
FINISHED |
| Object | sunrise views |
—
|
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: sunrise views | Statement: [Nihondaira, isScenicSpotFor, sunrise views]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isScenicSpotFor Context triple: [Nihondaira, isScenicSpotFor, sunrise views]
-
A.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
B.
isPartOfScenicVista
Indicates that something is included within, or contributes to, a larger scenic vista or panoramic view.
-
C.
naturalAttractionOf
chosen
Indicates a relationship where one entity is a natural feature or site that draws interest, attention, or visitors from another entity.
-
D.
isMajorAttractionFor
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
E.
isScenicArea
Indicates that a location is recognized as a scenic area, typically valued for its natural beauty or visually appealing surroundings.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63946708881908e441f37c8bd6fee |
completed | May 2, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:20 p.m.