Triple
T16246390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mala Osojnica |
E394380
|
entity |
| Predicate | photoSpotFor |
P33075
|
FINISHED |
| Object | postcard views of Lake Bled |
—
|
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: postcard views of Lake Bled | Statement: [Mala Osojnica, photoSpotFor, postcard views of Lake Bled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: photoSpotFor Context triple: [Mala Osojnica, photoSpotFor, postcard views of Lake Bled]
-
A.
hasPhotoSpot
Indicates that a location or entity includes or is associated with a designated place suitable for taking photographs.
-
B.
photographsTakenIn
Indicates that photographs were captured or taken within a specific location or place.
-
C.
oftenPhotographedAt
Indicates that an entity is frequently the subject of photographs taken at a particular location or during a specific event.
-
D.
photographedFrom
chosen
Indicates that one entity serves as the vantage point or location from which another entity is photographed.
-
E.
tourismImage
Indicates a relationship where something serves as a visual representation or promotional image associated with tourism for a place, attraction, or destination.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245931074819096f38003da70f271 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.