Triple
T15753382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brda |
E381903
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Dobrovo |
E1175874
|
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: Dobrovo | Statement: [Brda, hasSettlement, Dobrovo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dobrovo Context triple: [Brda, hasSettlement, Dobrovo]
-
A.
Dobrovo
chosen
Dobrovo is a small Slovenian village in the Goriška region, known as the cultural and economic hub of the Brda wine-growing area.
-
B.
Dušanovac
Dušanovac is an urban neighborhood of Belgrade, Serbia, known as a residential and commercial area within the municipality of Voždovac.
-
C.
Boždarevac
Boždarevac is a village located within the Barajevo municipality in the wider Belgrade region of Serbia.
-
D.
Borovo
Borovo is a small Bulgarian town situated along the Danube River in northern Bulgaria’s Ruse Province.
-
E.
Grbavica
Grbavica is a neighborhood in Sarajevo, Bosnia and Herzegovina, known for its residential blocks and its association with local football culture.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05031f6a08190bfb333eced0a59a1 |
completed | April 16, 2026, 2:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff9096d65c81908755cae83cc48e61 |
completed | May 9, 2026, 7:52 p.m. |
Created at: April 10, 2026, 4:47 a.m.