Triple
T4856483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospić |
E108548
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Smiljan |
E17957
|
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: Smiljan | Statement: [Gospić, hasNearbySettlement, Smiljan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Smiljan Context triple: [Gospić, hasNearbySettlement, Smiljan]
-
A.
Smiljan
chosen
Smiljan is a village in modern-day Croatia best known as the birthplace of inventor Nikola Tesla.
-
B.
Dudinka
Dudinka is a remote Arctic port town in northern Siberia, Russia, serving as a key shipping hub on the Yenisei River and gateway to the Norilsk industrial region.
-
C.
Ravanica
Ravanica is a river in central Serbia that flows through the region before joining the Velika Morava.
-
D.
Crnogorci
Crnogorci are a South Slavic ethnic group primarily associated with the country of Montenegro, known for their distinct cultural and historical identity in the Balkans.
-
E.
Crikvenica
Crikvenica is a coastal town and popular tourist resort on the Adriatic Sea in western Croatia.
- 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d3df75c8190830e2c927cc5a4f8 |
completed | March 20, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be6fac3fa0819085b7b732875a166b |
completed | March 21, 2026, 10:15 a.m. |
Created at: March 20, 2026, 1:26 p.m.