Triple
T12983331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bicocca |
E321703
|
entity |
| Predicate | casualtiesFrenchSwiss |
P14905
|
FINISHED |
| Object | heavy |
—
|
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: heavy | Statement: [Battle of Bicocca, casualtiesFrenchSwiss, heavy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesFrenchSwiss Context triple: [Battle of Bicocca, casualtiesFrenchSwiss, heavy]
-
A.
casualtiesFrancoBavarian
Indicates that there were casualties suffered by the Franco-Bavarian side in a particular conflict or event.
-
B.
FrancoSpanishCasualtiesKilledAndWounded
Indicates the number of people from Franco-Spanish forces who were killed or wounded as casualties in a conflict or event.
-
C.
FrenchCasualties
chosen
Indicates that the relationship specifies the number or extent of casualties suffered by French forces in a given event or context.
-
D.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
E.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:39 p.m.