Triple
T16472106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narrow Socialists |
E400088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bulgarian political party |
C347
|
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: Bulgarian political party Context triple: [Narrow Socialists, instanceOf, Bulgarian political party]
-
A.
Bulgarian politician
A Bulgarian politician is a public figure engaged in the governance and political life of Bulgaria, typically holding or seeking elected or appointed office at the local, regional, or national level.
-
B.
Pakistani political party
A Pakistani political party is an organized group of individuals in Pakistan that shares a common political ideology or agenda and seeks to gain and exercise governmental power through participation in elections and public policymaking.
-
C.
Irish political party
An Irish political party is an organized group in Ireland that seeks to influence or control government policy and decision-making by contesting elections and representing specific political ideologies or interests.
-
D.
former European Parliament political group
A former European Parliament political group is a now-defunct alliance of Members of the European Parliament (MEPs) that once organized around shared political goals or ideologies to coordinate legislative activity and representation within the Parliament.
-
E.
political party
chosen
A political party is an organized group of people who share common political ideals and policy goals and work together to gain and exercise governmental power through elections and public influence.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:11 a.m.