Triple
T14132110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeta Banovina |
E350193
|
entity |
| Predicate | historicalRegion |
P915
|
FINISHED |
| Object | Sandžak |
E163891
|
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: Sandžak | Statement: [Zeta Banovina, historicalRegion, Sandžak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sandžak Context triple: [Zeta Banovina, historicalRegion, Sandžak]
-
A.
Sandžak
chosen
Sandžak is a historically contested region in the western Balkans, straddling modern-day Serbia and Montenegro, known for its significant Bosniak population and multicultural heritage.
-
B.
Čukarica
Čukarica is a municipality of Belgrade known for its mix of urban neighborhoods, industrial zones, and green areas along the Sava River.
-
C.
Jurjev
Jurjev is a historical name for the Estonian city of Tartu, reflecting its past under various regional powers.
-
D.
Karašica
Karašica is a river in Croatia that flows through the Slavonia region before joining the Drava River.
-
E.
Krasin
Krasin is a historic Russian icebreaker, originally launched in the early 20th century, renowned for Arctic exploration and rescue missions.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610cece88190b4a86500677e5938 |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdf10e3948190b21968bc39094a8e |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 11:24 p.m.