Triple
T21330360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buttermere |
E525880
|
entity |
| Predicate | hasPhotographicFeature |
P121927
|
FINISHED |
| Object | reflections of surrounding fells |
—
|
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: reflections of surrounding fells | Statement: [Buttermere, hasPhotographicFeature, reflections of surrounding fells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhotographicFeature Context triple: [Buttermere, hasPhotographicFeature, reflections of surrounding fells]
-
A.
hasPhotogenicFeature
chosen
Indicates that an entity possesses a visual characteristic or attribute that is especially attractive or appealing when photographed.
-
B.
hasPhotoFeature
Indicates that an entity possesses a characteristic, capability, or option specifically related to photos or photography.
-
C.
hasAIPhotoFeatures
Indicates that an entity provides or supports photo-related features powered by artificial intelligence.
-
D.
isPhotographicSubject
Indicates that an entity serves as the subject or main focus captured in a photograph taken by another entity.
-
E.
hasPhotographicIcon
Indicates that an entity is associated with or represented by a photographic image or icon.
- 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7ab5177dc8190b888351e9a45b45f |
completed | April 21, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:42 p.m.