Triple
T17743007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasil Levski |
E442910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national hero of Bulgaria |
C39625
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: national hero of Bulgaria Context triple: [Vasil Levski, instanceOf, national hero of Bulgaria]
-
A.
national hero of Russia
A national hero of Russia is an individual, real or legendary, who is widely celebrated for extraordinary courage, sacrifice, or leadership in defending or advancing the Russian state and its people.
-
B.
national hero of Poland
A national hero of Poland is an individual, often historical or military, who is widely revered for extraordinary acts of courage, sacrifice, or leadership that significantly advanced Polish independence, freedom, or cultural identity.
-
C.
Serbian national hero
A Serbian national hero is an individual, real or legendary, celebrated in Serbian history and culture for extraordinary courage, sacrifice, or leadership in defending the nation’s freedom, identity, or values.
-
D.
national hero of Wales
A national hero of Wales is an individual, real or legendary, who is celebrated for embodying Welsh identity, culture, and values through exceptional acts of courage, leadership, or contribution to the nation’s history.
-
E.
national hero of Mexico
A national hero of Mexico is an individual, often a historical figure, who is widely honored and celebrated for extraordinary contributions to the country’s independence, identity, social justice, or cultural legacy.
- F. None of above. chosen
Provenance (1 batch)
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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:09 a.m.