Triple
T16377280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberal Wars era |
E397708
|
entity |
| Predicate | mainBelligerentSide2 |
P375
|
FINISHED |
| Object | Miguelite forces loyal to Miguel I |
—
|
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: Miguelite forces loyal to Miguel I | Statement: [Liberal Wars era, mainBelligerentSide2, Miguelite forces loyal to Miguel I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainBelligerentSide2 Context triple: [Liberal Wars era, mainBelligerentSide2, Miguelite forces loyal to Miguel I]
-
A.
warAdversary
Indicates that two entities are opponents or enemies engaged in a state of war or armed conflict.
-
B.
countryOfVictoriousSide
Indicates the country to which the winning or victorious side in a conflict, competition, or contest belongs.
-
C.
conflictSide
chosen
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
D.
countryOfDefeatedSide
Indicates the country to which the losing or defeated side in a conflict, competition, or confrontation belongs.
-
E.
alliesInWar
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319d8a40c8190af37e7ed60b9c4dd |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.