Triple
T7900955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridal Veil Falls (Provo Canyon) |
E183449
|
entity |
| Predicate | isFrequentlyPhotographed |
P17748
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bridal Veil Falls (Provo Canyon), isFrequentlyPhotographed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFrequentlyPhotographed Context triple: [Bridal Veil Falls (Provo Canyon), isFrequentlyPhotographed, true]
-
A.
oftenPhotographedAt
chosen
Indicates that an entity is frequently the subject of photographs taken at a particular location or during a specific event.
-
B.
photographedByTourists
Indicates that the subject has been photographed by people visiting as tourists.
-
C.
hasPhotoSpot
Indicates that a location or entity includes or is associated with a designated place suitable for taking photographs.
-
D.
hasPhotographicSignificance
Indicates that something holds notable importance or relevance in the context of photography, such as for documentation, artistic value, or visual record.
-
E.
isFrequentlyRecorded
Indicates that an entity is captured or documented many times within a given dataset, medium, or context.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a3f4c2c81909ae70b0acf4729be |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:02 p.m.