Triple
T26516593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Rymnik |
E669828
|
entity |
| Predicate | casualtiesRussianAustrian |
P82956
|
FINISHED |
| Object | relatively light |
—
|
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 | Statement: [Battle of Rymnik, casualtiesRussianAustrian, relatively light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesRussianAustrian Context triple: [Battle of Rymnik, casualtiesRussianAustrian, relatively light]
-
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.
militaryCasualtiesSide
chosen
Indicates the side or party in a conflict to which the recorded military casualties belong.
-
D.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
E.
casualties
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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 1:24 a.m.