Triple
T35663230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Skalitz |
E1030493
|
entity |
| Predicate | sideWithHigherCasualties |
P82956
|
FINISHED |
| Object | Austrian Empire |
—
|
NE NERFINISHED |
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: Austrian Empire | Statement: [Battle of Skalitz, sideWithHigherCasualties, Austrian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideWithHigherCasualties Context triple: [Battle of Skalitz, sideWithHigherCasualties, Austrian Empire]
-
A.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
B.
sustainedHeavyCasualtiesAt
Indicates that an entity experienced a large number of serious losses (e.g., deaths or injuries) at a specific location or during a specific event.
-
C.
militaryCasualtiesSide
chosen
Indicates the side or party in a conflict to which the recorded military casualties belong.
-
D.
primaryCasualtiesFrom
Indicates that an entity is the main source or cause of the casualties experienced by another entity.
-
E.
militaryCasualtiesEstimate
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79faacec48190a5738e030b6f8808 |
completed | May 3, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.