Triple
T20514420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magdeburg's Wedding |
E503646
|
entity |
| Predicate | hasEstimatedCasualties |
P661
|
FINISHED |
| Object | approximately 20,000–25,000 dead |
—
|
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: approximately 20,000–25,000 dead | Statement: [Magdeburg's Wedding, hasEstimatedCasualties, approximately 20,000–25,000 dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstimatedCasualties Context triple: [Magdeburg's Wedding, hasEstimatedCasualties, approximately 20,000–25,000 dead]
-
A.
casualtiesEstimate
chosen
Indicates an estimated number of people killed, injured, or otherwise harmed as a result of an event or incident.
-
B.
militaryCasualtiesEstimate
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
C.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
D.
hasCasualtiesLevel
Indicates the severity or extent of casualties associated with an event, incident, or situation.
-
E.
plannedCasualtyExpectations
Indicates that an entity has estimated or anticipated the number or extent of casualties expected to result from a planned action or event.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f4133048190abb777be4b65c2c4 |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.