Triple
T16046378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sveta Gora |
E389230
|
entity |
| Predicate | hasViewOf |
P854
|
FINISHED |
| Object | Vipava Valley |
E381900
|
NE 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: Vipava Valley | Statement: [Sveta Gora, hasViewOf, Vipava Valley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vipava Valley Context triple: [Sveta Gora, hasViewOf, Vipava Valley]
-
A.
Vipava Valley
chosen
Vipava Valley is a picturesque wine-growing region in western Slovenia known for its mild climate, karst landscapes, and historic villages.
-
B.
Soča Valley
The Soča Valley is a picturesque alpine valley in western Slovenia, renowned for its emerald-green Soča River, outdoor sports, and World War I history.
-
C.
Bohinj Valley
Bohinj Valley is a picturesque alpine valley in northwestern Slovenia, renowned for its unspoiled nature, traditional villages, and the glacial Lake Bohinj at its heart.
-
D.
Savski Venac
Savski Venac is a central urban municipality of Belgrade, Serbia, known for its government institutions, major transport hubs, and historic neighborhoods.
-
E.
Vipava
Vipava is a small Slovenian town known for its picturesque wine-growing valley, numerous springs, and historic architecture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1835dd9a0819087e362cf5770232a |
completed | April 17, 2026, 12:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0025ef00548190b802b4aaba907aa2 |
completed | May 10, 2026, 6:30 a.m. |
Created at: April 10, 2026, 4:56 a.m.