Triple
T7670244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoran Janković |
E173728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Slovenian politician |
C9453
|
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: Slovenian politician Context triple: [Zoran Janković, instanceOf, Slovenian politician]
-
A.
Slovenian person
chosen
A Slovenian person is an individual who is a citizen or native of Slovenia, typically sharing in its South Slavic cultural, historical, and linguistic heritage.
-
B.
Yugoslav politician
A Yugoslav politician is a public official or political leader who operated within the federal structures, republics, or local governments of the former Socialist Federal Republic of Yugoslavia, shaping its domestic and foreign policies during its existence.
-
C.
Czechoslovak politician
A Czechoslovak politician is a public figure who held governmental or party office in the former state of Czechoslovakia, influencing its domestic and foreign policies before its dissolution in 1993.
-
D.
Hungarian politician
A Hungarian politician is a public figure who participates in the governance and political decision-making processes of Hungary, typically by holding or seeking elected or appointed office at the local, regional, or national level.
-
E.
Bosnian Serb politician
A Bosnian Serb politician is a public official or political figure of Serb ethnicity from Bosnia and Herzegovina who participates in the governance, representation, or political processes of the country, often within the context of its complex ethnic and administrative structures.
- F. None of above.
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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4 p.m.