Triple
T854332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Wagram |
E18455
|
entity |
| Predicate | AustrianStrength |
P20640
|
FINISHED |
| Object | about 140000 soldiers |
—
|
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 140000 soldiers | Statement: [Battle of Wagram, AustrianStrength, about 140000 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AustrianStrength Context triple: [Battle of Wagram, AustrianStrength, about 140000 soldiers]
-
A.
strengthRussoAustrian
Indicates the relative military or political strength between Russian and Austrian forces or interests in a given context.
-
B.
languageOnAustrianSide
Indicates that a particular language is used or present on the Austrian side of a border, context, or interaction.
-
C.
RussoAustrianObjective
Indicates a shared objective or goal jointly pursued by Russian and Austrian parties or forces.
-
D.
endOfMonarchicalRuleInAustria
Indicates the point in time or event marking the cessation of monarchical governance in Austria.
-
E.
compensatedAustriaForLossOf
Indicates that an entity provided compensation to Austria for a specific loss or damage.
- F. None of above. chosen
Provenance (4 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac3a48c08190b4677d825fcbfaf9 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa81ef348190b067f817574e9efe |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4893e481908632102d240466dc |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.