Triple
T13576470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guillermón Moncada |
E324298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cuban independence fighter |
C24195
|
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: Cuban independence fighter Context triple: [Guillermón Moncada, instanceOf, Cuban independence fighter]
-
A.
Colombian independence hero
A Colombian independence hero is a historical figure who played a pivotal role in leading, organizing, or inspiring the struggle to liberate Colombia from Spanish colonial rule in the early 19th century.
-
B.
Latin American independence leader
chosen
A Latin American independence leader is a historical figure who organized, inspired, and directed political and military efforts to liberate Latin American territories from colonial rule and establish sovereign nations.
-
C.
Mexican independence activist
A Mexican independence activist is an individual who actively worked—politically, militarily, or socially—to challenge Spanish colonial rule and promote the cause of an autonomous Mexican nation during the late 18th and early 19th centuries.
-
D.
Cuban military officer
A Cuban military officer is a commissioned leader in Cuba’s armed forces responsible for commanding troops, planning and executing military operations, and upholding national defense and security policies.
-
E.
Chilean independence hero
A Chilean independence hero is a historical figure who played a pivotal role in leading, organizing, or inspiring Chile’s struggle to break free from Spanish colonial rule and establish a sovereign nation.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:48 p.m.