Triple
T36454978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goraiko (sunrise from Mount Fuji summit) |
E898126
|
entity |
| Predicate | isViewedTowards |
P127904
|
FINISHED |
| Object | eastern horizon |
—
|
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: eastern horizon | Statement: [Goraiko (sunrise from Mount Fuji summit), isViewedTowards, eastern horizon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isViewedTowards Context triple: [Goraiko (sunrise from Mount Fuji summit), isViewedTowards, eastern horizon]
-
A.
hasViewingSide
Indicates that one entity serves as the side or surface of another entity that is intended to be viewed or observed.
-
B.
viewingIs
Indicates that one entity is engaged in the act or state of viewing, observing, or watching another entity.
-
C.
hasViewThrough
Indicates that one entity can be seen or visually perceived through another entity acting as an intermediate medium or opening.
-
D.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
E.
hasViewingPointFor
chosen
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.