Triple
T16790611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dojran |
E408098
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Star Dojran |
E399900
|
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: Star Dojran | Statement: [Dojran, hasPart, Star Dojran]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Star Dojran Context triple: [Dojran, hasPart, Star Dojran]
-
A.
Star Dojran
chosen
Star Dojran is a small lakeside town in southeastern North Macedonia known as a local tourist and fishing center on the shores of Lake Dojran.
-
B.
Malko Tarnovo
Malko Tarnovo is a small town in southeastern Bulgaria near the Turkish border, known as the only Bulgarian settlement within the Strandzha Nature Park.
-
C.
Dimitar
Dimitar is a masculine given name of Slavic origin, commonly used in Bulgaria and other Eastern European countries.
-
D.
Borjan
Borjan is a surname most notably borne by Milan Borjan, a Canadian professional soccer goalkeeper.
-
E.
Radev
Radev is a Bulgarian surname most prominently associated with Rumen Radev, the President of Bulgaria and former Air Force commander.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a5d10c8190a581de79e4f7ccfa |
completed | April 18, 2026, 4:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00ab0c39108190a332fdc78c053628 |
completed | May 10, 2026, 3:58 p.m. |
Created at: April 10, 2026, 5:22 a.m.