Triple
T26563157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Battle of Mohács |
E666304
|
entity |
| Predicate | casualtiesHabsburgSide |
P82956
|
FINISHED |
| Object | relatively light casualties |
—
|
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: relatively light casualties | Statement: [Second Battle of Mohács, casualtiesHabsburgSide, relatively light casualties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesHabsburgSide Context triple: [Second Battle of Mohács, casualtiesHabsburgSide, relatively light casualties]
-
A.
AustrianCasualtiesApprox
Indicates an approximate number or estimate of casualties suffered by Austrian forces or entities.
-
B.
militaryCasualtiesSide
chosen
Indicates the side or party in a conflict to which the recorded military casualties belong.
-
C.
combatantStrengthHabsburg
Indicates the relative military strength or capability of a combatant in relation to the Habsburg side in a conflict.
-
D.
casualtiesFrancoBavarian
Indicates that there were casualties suffered by the Franco-Bavarian side in a particular conflict or event.
-
E.
combatantStrengthAustrianSide
Indicates that the associated entity represents the strength or size of the Austrian side’s combatant forces in a 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:53 a.m.