Triple
T20025421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Wertingen |
E494969
|
entity |
| Predicate | AustrianPrisoners |
P87171
|
FINISHED |
| Object | about 2,900 captured |
—
|
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: about 2,900 captured | Statement: [Battle of Wertingen, AustrianPrisoners, about 2,900 captured]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AustrianPrisoners Context triple: [Battle of Wertingen, AustrianPrisoners, about 2,900 captured]
-
A.
AustrianPrisonersTakenApproximate
chosen
Indicates that an approximate number of Austrian prisoners were taken or captured in a given context or event.
-
B.
numberOfPrisonersDuringWar
Indicates the count of prisoners held during a specified war or wartime period.
-
C.
associatedConcentrationCamp
Indicates a relationship where an entity is linked or connected to a specific concentration camp, typically by location, administration, or operational association.
-
D.
AustrianGunsCaptured
Indicates that guns belonging to Austrian forces were seized and taken by another party.
-
E.
concentrationCampDestination
Indicates that an entity is sent or transported to a concentration camp as its destination.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628d5b8c8190a35f95ac4a016550 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:35 p.m.