Triple
T5117591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arda River |
E115374
|
entity |
| Predicate | nearSettlement |
P3883
|
FINISHED |
| Object | Smolyan |
E314046
|
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: Smolyan | Statement: [Arda River, nearSettlement, Smolyan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Smolyan Context triple: [Arda River, nearSettlement, Smolyan]
-
A.
Smolyan
chosen
Smolyan is a Bulgarian town known as an administrative, cultural, and tourist center in the Rhodope Mountains.
-
B.
Pliska
Pliska was the first capital city of the early medieval First Bulgarian Empire, serving as its political and administrative center.
-
C.
Bansko
Bansko is a Bulgarian mountain town renowned as one of Eastern Europe’s leading ski and winter sports resorts.
-
D.
Asenovgrad
Asenovgrad is a town in southern Bulgaria known as a gateway to the Rhodope Mountains and a regional center rich in historical and religious landmarks.
-
E.
Ivaylovgrad
Ivaylovgrad is a small town in southern Bulgaria known for its proximity to the Greek border, scenic river valley landscapes, and nearby archaeological and historical sites.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd77ccb19c8190844c628ff7cfcca2 |
completed | March 20, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bed9185b9481908afd32bdeefa3f1e |
completed | March 21, 2026, 5:44 p.m. |
Created at: March 20, 2026, 1:41 p.m.