Triple
T31083428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Calcinato |
E792163
|
entity |
| Predicate | AustrianAllies |
P58473
|
FINISHED |
| Object | Imperial German contingents |
—
|
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: Imperial German contingents | Statement: [Battle of Calcinato, AustrianAllies, Imperial German contingents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AustrianAllies Context triple: [Battle of Calcinato, AustrianAllies, Imperial German contingents]
-
A.
AustrianArmy
Indicates that an entity is the Austrian Army or is serving as part of the Austrian Army in a given context.
-
B.
involvedUnitAustrian
Indicates that an Austrian military or organizational unit was involved as a participant in the referenced event or activity.
-
C.
combatantCommanderAustria
Indicates that the referenced entity served as a military commander for Austria in a particular conflict or combat situation.
-
D.
involvedUnitAustriaHungary
chosen
Indicates that the unit or force specified was involved on behalf of Austria-Hungary in the referenced event or conflict.
-
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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695fb5f60819099ac1f20472cfc61 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.