Triple
T30090549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Worth |
E764719
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mexican–American War veteran |
C10597
|
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–American War veteran Context triple: [William Worth, instanceOf, Mexican–American War veteran]
-
A.
participant in the Mexican–American War
chosen
A participant in the Mexican–American War is an individual, military unit, or organized group that actively took part in the planning, fighting, support, or decision-making activities of the 1846–1848 conflict between Mexico and the United States.
-
B.
Mexican army officer
A Mexican army officer is a commissioned leader in Mexico’s armed forces responsible for planning, directing, and overseeing military operations, personnel, and resources in defense of the nation.
-
C.
Mexican general
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.
-
D.
event in the Mexican–American War
An "event in the Mexican–American War" is a specific historical occurrence—such as a battle, campaign, treaty, or political decision—that took place between 1846 and 1848 in the context of the conflict between Mexico and the United States.
-
E.
military personnel of the Spanish–American War
Individuals who served in the armed forces of any nation involved in the Spanish–American War of 1898, including soldiers, sailors, and support staff engaged in its military operations.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:05 p.m.