Triple
T21771660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesenice, Slovenia |
E537446
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Radovljica |
—
|
NE NERFINISHED |
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: Radovljica | Statement: [Jesenice, Slovenia, locatedNear, Radovljica]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Radovljica Context triple: [Jesenice, Slovenia, locatedNear, Radovljica]
-
A.
Radovljica
chosen
Radovljica is a historic town in northwestern Slovenia known for its well-preserved medieval old town and cultural heritage.
-
B.
Trpanj
Trpanj is a coastal town and popular tourist destination on Croatia’s Pelješac Peninsula, known for its beaches, ferry port, and Mediterranean charm.
-
C.
Grožnjan
Grožnjan is a small medieval hilltop town in Istria, Croatia, renowned as an artists’ colony and cultural center.
-
D.
Šentjur
Šentjur is a Slovenian basketball club competing in the country’s top professional league.
-
E.
Gložan
Gložan is a village in the Vojvodina region of northern Serbia, known for its Slovak ethnic community and agricultural character.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031aea8c88190b4bc57df6f269ba6 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 16, 2026, 6:51 p.m.