Triple
T28477618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | urban underground of the 26th of July Movement |
E720604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revolutionary underground network |
C49412
|
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: revolutionary underground network Context triple: [urban underground of the 26th of July Movement, instanceOf, revolutionary underground network]
-
A.
underground network
chosen
An underground network is a covert, often informal system of interconnected individuals, groups, or infrastructure that operates out of public view to share resources, information, or influence.
-
B.
underground alliance
An underground alliance is a covert coalition of individuals or groups who secretly collaborate to resist, subvert, or overthrow an established power or oppressive system.
-
C.
organización revolucionaria
Una organización revolucionaria es una entidad colectiva estructurada que busca transformar radicalmente el orden social, político o económico existente mediante la acción coordinada y sostenida.
-
D.
clandestine group
A clandestine group is a secretive organization whose members covertly coordinate activities, often to pursue hidden political, criminal, or subversive objectives while avoiding detection by authorities or the public.
-
E.
revolutionary society
A revolutionary society is a social organization or community fundamentally structured around initiating, supporting, or institutionalizing radical political, economic, or cultural change that breaks sharply from existing systems.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:53 a.m.