Triple
T2763412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Bulgarian Empire |
E61275
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Preslav |
E102446
|
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: Preslav | Statement: [Second Bulgarian Empire, majorCity, Preslav]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Preslav Context triple: [Second Bulgarian Empire, majorCity, Preslav]
-
A.
Preslav
chosen
Preslav is an ancient Bulgarian city that served as a major medieval political and cultural capital of the First Bulgarian Empire and a key center of Slavic literacy and Orthodox Christianity.
-
B.
Ilija
Ilija is a masculine given name of Slavic origin, commonly used in countries such as Bulgaria, Serbia, and North Macedonia.
-
C.
Petar
Petar is a given name commonly used in Slavic countries, equivalent to the English name Peter.
-
D.
Miroslav
Miroslav is a common Slavic male given name, notably borne by Slovak ice hockey star Miroslav Šatan.
-
E.
Saša
Saša is a given name commonly used in Slavic countries, often as a diminutive of Aleksandar or Aleksandra.
- 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_69ab4b7bab6c8190a5c2efef19a8ef34 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdd5291d88190a7347af947a2a564 |
completed | March 7, 2026, 8:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afc04630b8819081cd8ddac1d42184 |
completed | March 10, 2026, 6:55 a.m. |
Created at: March 6, 2026, 9:57 p.m.