Triple
T8291128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokolica |
E193897
|
entity |
| Predicate | panorama |
P29603
|
FINISHED |
| Object | Pieniny and Tatra Mountains in distance |
—
|
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: Pieniny and Tatra Mountains in distance | Statement: [Sokolica, panorama, Pieniny and Tatra Mountains in distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: panorama Context triple: [Sokolica, panorama, Pieniny and Tatra Mountains in distance]
-
A.
hasPanoramicView
chosen
Indicates that something offers a wide, unobstructed view over a broad surrounding area.
-
B.
parallax
Indicates the apparent shift in an object’s position relative to a background when observed from two different viewpoints or at two different times.
-
C.
hasSummitPanorama
Indicates that a summit location offers a panoramic view or image captured from its highest point.
-
D.
perspectiveOf
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
-
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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c9b65e0819083ddc82fb7c4a5f3 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:52 p.m.