Triple
T13933766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emiliano Zapata |
E335056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mexican military leader |
C9426
|
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: Mexican military leader Context triple: [Emiliano Zapata, instanceOf, Mexican military leader]
-
A.
Mexican general
chosen
A Mexican general is a high-ranking military officer in Mexico’s armed forces responsible for leading troops, planning and executing military operations, and contributing to national defense and security strategy.
-
B.
Argentine general
An Argentine general is a high-ranking military officer in Argentina's armed forces responsible for leading large military units, planning and executing national defense strategies, and advising political authorities on security and defense matters.
-
C.
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.
-
D.
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.
-
E.
Dominican military officer
A Dominican military officer is a commissioned member of the Dominican Republic’s armed forces responsible for leading troops, planning and executing military operations, and upholding national defense and security.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:17 p.m.