Triple
T18550066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sisak |
E453348
|
entity |
| Predicate | casualtiesHabsburgCroatian |
P1399
|
FINISHED |
| Object | hundreds killed and wounded |
—
|
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: hundreds killed and wounded | Statement: [Battle of Sisak, casualtiesHabsburgCroatian, hundreds killed and wounded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesHabsburgCroatian Context triple: [Battle of Sisak, casualtiesHabsburgCroatian, hundreds killed and wounded]
-
A.
AustrianCasualtiesApprox
Indicates an approximate number or estimate of casualties suffered by Austrian forces or entities.
-
B.
casualtiesFrancoBavarian
Indicates that there were casualties suffered by the Franco-Bavarian side in a particular conflict or event.
-
C.
casualtiesGothic
Indicates that an event or action resulted in casualties specifically among Gothic people or forces.
-
D.
combatantStrengthHabsburg
Indicates the relative military strength or capability of a combatant in relation to the Habsburg side in a conflict.
-
E.
casualties
chosen
Indicates that an event, action, or situation resulted in people being killed or injured.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534beeb408190a03f6d7c3f2ef389 |
completed | April 19, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.