Triple
T17016819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pwersa ng Masang Pilipino |
E412841
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Philippine 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: Philippine political party Context triple: [Pwersa ng Masang Pilipino, instanceOf, Philippine political party]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Peruvian political party
A Peruvian political party is an organized group of individuals in Peru that shares a common political ideology or agenda and seeks to gain and exercise governmental power through participation in elections and public policy-making.
-
E.
Filipino American organization
A Filipino American organization is a group formed by and for Filipino Americans to promote cultural heritage, community support, advocacy, and social or professional networking within the Filipino diaspora in the United States.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:33 a.m.