Triple
T20153371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organisation de résistance de l'armée |
E491492
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military resistance organization |
C859
|
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: military resistance organization Context triple: [Organisation de résistance de l'armée, instanceOf, military resistance organization]
-
A.
resistance movement
A resistance movement is an organized effort by a group of people to oppose, undermine, or overthrow an existing power, authority, or occupying force, often through political, social, or guerrilla actions.
-
B.
Jewish resistance organization
A Jewish resistance organization is a clandestine or organized group formed by Jews to oppose, sabotage, or survive oppressive regimes, antisemitic persecution, or genocidal policies through political, military, cultural, or humanitarian means.
-
C.
paramilitary organization
chosen
A paramilitary organization is a structured group that operates with military-style training, hierarchy, and tactics but is not formally part of a recognized state's official armed forces.
-
D.
Polish resistance organization
A Polish resistance organization is a clandestine group formed in Poland to oppose and undermine occupying or oppressive regimes through coordinated political, military, and intelligence activities.
-
E.
communist military organization
A communist military organization is an armed group structured under communist ideology, aiming to defend, expand, or enforce a socialist or communist political system through organized military means.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
Created at: April 11, 2026, 11:34 p.m.