Triple
T21769438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FrP |
E537384
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norwegian political party |
C41423
|
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: Norwegian political party Context triple: [FrP, instanceOf, Norwegian political party]
-
A.
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.
-
B.
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.
-
C.
Norwegian resistance organization
A Norwegian resistance organization is a clandestine group formed to oppose and undermine occupying or oppressive forces in Norway through activities such as intelligence gathering, sabotage, and support for the civilian population.
-
D.
Norwegian organization
chosen
A Norwegian organization is an entity based in Norway, such as a company, association, or institution, that is formally structured to pursue specific economic, social, cultural, or public objectives under Norwegian law.
-
E.
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.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:51 p.m.