Triple
T28950326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albena Denkova / Maxim Staviski |
E730993
|
entity |
| Predicate | BulgarianNationalTitleCount |
P166056
|
FINISHED |
| Object | multiple |
—
|
LITERAL 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: multiple | Statement: [Albena Denkova / Maxim Staviski, BulgarianNationalTitleCount, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BulgarianNationalTitleCount Context triple: [Albena Denkova / Maxim Staviski, BulgarianNationalTitleCount, multiple]
-
A.
nameInBulgarian
Indicates that an entity is referred to by a specific name when expressed in the Bulgarian language.
-
B.
officeHolderTitleInBulgarian
Indicates the official title or designation of an office holder as expressed in the Bulgarian language.
-
C.
EuropeanTitleCount
Indicates the number of European titles (such as championships or major continental honors) that an entity has won or holds.
-
D.
strengthBulgaria
Indicates a relationship where something possesses or demonstrates strength specifically associated with Bulgaria.
-
E.
primaryBulgarLeaderTitle
Indicates the official title held by the main or highest-ranking leader in Bulgaria.
- F. None of above. chosen
Provenance (4 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65bb75cd08190bbdb63c093ad6210 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 8:43 a.m.