Triple
T16575363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bud Bagsak assault |
E402695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engagement of the Moro Rebellion |
C37653
|
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: engagement of the Moro Rebellion Context triple: [Bud Bagsak assault, instanceOf, engagement of the Moro Rebellion]
-
A.
engagement of the Philippine–American War
An engagement of the Philippine–American War is a distinct military encounter or operation between U.S. and Filipino forces, occurring at a specific time and place, that contributes to the broader course and outcome of the conflict.
-
B.
engagement of the Mexican–American War
The "engagement of the Mexican–American War" class represents individual military encounters—ranging from skirmishes to major battles—between Mexican and United States forces during the 1846–1848 conflict, including their participants, locations, dates, and outcomes.
-
C.
engagement of the Peninsular War
An engagement of the Peninsular War is a specific military action or battle fought between Napoleonic French forces and their Iberian and British opponents on the Iberian Peninsula between 1807 and 1814.
-
D.
Javanese military campaign
A Javanese military campaign is a coordinated series of armed operations conducted by Javanese polities or forces to achieve specific political, territorial, or strategic objectives.
-
E.
engagement of the Russo-Japanese War
An engagement of the Russo-Japanese War is a discrete military encounter—on land, sea, or both—between Russian and Japanese forces during the 1904–1905 conflict, characterized by specific participants, location, timeframe, and tactical objectives.
- F. None of above. chosen
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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:16 a.m.