Triple
T22426630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenashdale Falls |
E554385
|
entity |
| Predicate | hasPhotographicViewpoints |
P96770
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Glenashdale Falls, hasPhotographicViewpoints, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhotographicViewpoints Context triple: [Glenashdale Falls, hasPhotographicViewpoints, yes]
-
A.
hasViewingPointFor
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
-
B.
hasScenicViewpoints
chosen
Indicates that something includes or provides locations specifically intended for enjoying scenic or panoramic views.
-
C.
hasPanoramicView
Indicates that something offers a wide, unobstructed view over a broad surrounding area.
-
D.
hasPhotogenicFeature
Indicates that an entity possesses a visual characteristic or attribute that is especially attractive or appealing when photographed.
-
E.
hasViewingAngles
Indicates that one entity possesses or is characterized by specific viewing angles relative to another entity or reference frame.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2e438481908d43026727afa709 |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.