Triple
T24191678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Army in World War II |
E599715
|
entity |
| Predicate | changeOfSide |
P60050
|
FINISHED |
| Object | after Armistice of Cassibile |
—
|
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: after Armistice of Cassibile | Statement: [Italian Army in World War II, changeOfSide, after Armistice of Cassibile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeOfSide Context triple: [Italian Army in World War II, changeOfSide, after Armistice of Cassibile]
-
A.
switchedSidesIn
chosen
Indicates that an entity changed allegiance or affiliation from one side to another within a specified conflict, group, or context.
-
B.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
-
C.
tacticalChange
Indicates a deliberate adjustment in strategy, methods, or actions made to improve effectiveness in a specific situation or operation.
-
D.
changesAllianceOf
Indicates that one entity causes or initiates a change in the alliance or affiliation status of another entity.
-
E.
targetSide
Indicates the specific side or aspect of a referenced target that is involved in or affected by the relationship or action.
- 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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:35 p.m.