Triple
T8616580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ulm |
E204053
|
entity |
| Predicate | hasAustrianCasualtiesAndCaptures |
P22214
|
FINISHED |
| Object | over 60,000 |
—
|
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: over 60,000 | Statement: [Battle of Ulm, hasAustrianCasualtiesAndCaptures, over 60,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAustrianCasualtiesAndCaptures Context triple: [Battle of Ulm, hasAustrianCasualtiesAndCaptures, over 60,000]
-
A.
AustrianCasualtiesApprox
chosen
Indicates an approximate number or estimate of casualties suffered by Austrian forces or entities.
-
B.
AustrianGunsCaptured
Indicates that guns belonging to Austrian forces were seized and taken by another party.
-
C.
AustrianGunsLost
Indicates that certain guns or artillery pieces belonging to Austrian forces were lost.
-
D.
combatantCommanderAustria
Indicates that the referenced entity served as a military commander for Austria in a particular conflict or combat situation.
-
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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4703b57c81909511de72fa5c38d7 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.