Triple
T37187123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barisan Alternatif |
E921348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Malaysian political alliance |
C64321
|
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: Malaysian political alliance Context triple: [Barisan Alternatif, instanceOf, Malaysian political alliance]
-
A.
Indian political alliance
An Indian political alliance is a coalition of two or more political parties in India that collaborate to contest elections, share resources, and pursue common policy goals while retaining their individual identities.
-
B.
Italian political alliance
An Italian political alliance is a coalition of two or more Italian political parties that coordinate their electoral strategies and policy platforms to increase their collective influence in government and parliament.
-
C.
political-military alliance
A political-military alliance is a formal agreement between two or more states to coordinate their defense and foreign policies, often including mutual security guarantees and joint military planning.
-
D.
Iraqi political party
An Iraqi political party is an organized group within Iraq that seeks to influence or control government policy and leadership through participation in the country’s political processes and elections.
-
E.
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.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.