Triple
T11227831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujinomiya Trail |
E265740
|
entity |
| Predicate | viewFeatures |
P41649
|
FINISHED |
| Object | panoramic sunrise views from near the summit |
—
|
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: panoramic sunrise views from near the summit | Statement: [Fujinomiya Trail, viewFeatures, panoramic sunrise views from near the summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewFeatures Context triple: [Fujinomiya Trail, viewFeatures, panoramic sunrise views from near the summit]
-
A.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
B.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
-
C.
viewTechnologyIn
Indicates that a technology is being viewed, examined, or accessed within a particular context, location, or environment.
-
D.
displaysFeature
chosen
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of another entity.
-
E.
viewTechnology
Indicates that an entity observes, inspects, or examines a particular technology.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ff7b40819089c835be710bc575 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.