Triple
T34787934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Serbia |
E1002863
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Serbian political party |
C38674
|
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: Serbian political party Context triple: [United Serbia, instanceOf, Serbian political party]
-
A.
Bosnian Serb political party
A Bosnian Serb political party is an organized group representing the political interests, national identity, and policy preferences of ethnic Serbs within Bosnia and Herzegovina’s political system.
-
B.
Hungarian political party
A Hungarian political party is an organized group within Hungary that seeks to influence or control government policy and leadership by contesting elections and representing specific ideological, social, or economic interests.
-
C.
Romanian political party
A Romanian political party is an organized group of individuals in Romania that shares a common political ideology or set of policy goals and seeks to gain and exercise political power through participation in elections and governance.
-
D.
Serbian politician
A Serbian politician is a public figure engaged in the governance and political processes of Serbia, participating in decision-making, policy development, and representation of citizens at local, regional, or national levels.
-
E.
Serbian organization
chosen
A Serbian organization is a structured group or entity based in Serbia that coordinates people and resources to pursue specific social, economic, cultural, political, or charitable objectives within the Serbian context.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.