Triple
T27510783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andean theater of the Spanish American wars of independence |
E694404
|
entity |
| Predicate | mainBelligerentSide |
P375
|
FINISHED |
| Object | royalist forces |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: royalist forces | Statement: [Andean theater of the Spanish American wars of independence, mainBelligerentSide, royalist forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainBelligerentSide Context triple: [Andean theater of the Spanish American wars of independence, mainBelligerentSide, royalist forces]
-
A.
majorBelligerent
Indicates that an entity is a primary or principal participant in a conflict, war, or large-scale hostile engagement.
-
B.
conflictSide
chosen
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
C.
forzaBelligerante
Indicates a party’s status or role as a belligerent force engaged in a conflict or war.
-
D.
warAdversary
Indicates that two entities are opponents or enemies engaged in a state of war or armed conflict.
-
E.
countryOfVictoriousSide
Indicates the country to which the winning or victorious side in a conflict, competition, or contest belongs.
- F. None of above.
Provenance (3 batches)
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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ef94b488190825d38e24496b755 |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:16 p.m.