Triple
T38263822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Arbedo |
E1017997
|
entity |
| Predicate | hasApproximateSwissCasualties |
P661
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Battle of Arbedo, hasApproximateSwissCasualties, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateSwissCasualties Context triple: [Battle of Arbedo, hasApproximateSwissCasualties, high]
-
A.
casualtiesSwiss
Indicates that an event or action resulted in Swiss individuals being killed, injured, or otherwise harmed.
-
B.
militaryCasualtiesEstimate
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
C.
casualtiesEstimate
chosen
Indicates an estimated number of people killed, injured, or otherwise harmed as a result of an event or incident.
-
D.
approximateNorwegianCasualties
Indicates an estimated or rough count of Norwegian casualties resulting from a particular event or situation.
-
E.
AustrianCasualtiesApprox
Indicates an approximate number or estimate of casualties suffered by Austrian forces or entities.
- 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: May 3, 2026, 4:30 p.m.