Triple
T13851679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Soor |
E332957
|
entity |
| Predicate | strengthAustria |
P20640
|
FINISHED |
| Object | approximately 30,000 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: approximately 30,000 soldiers | Statement: [Battle of Soor, strengthAustria, approximately 30,000 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthAustria Context triple: [Battle of Soor, strengthAustria, approximately 30,000 soldiers]
-
A.
AustrianStrength
chosen
Indicates a relationship where an entity possesses or exhibits strength specifically associated with Austria, such as Austrian power, influence, or capability.
-
B.
strengthRussoAustrian
Indicates the relative military or political strength between Russian and Austrian forces or interests in a given context.
-
C.
strengthAustriaSaxony
Indicates the relative military or political strength between Austria and Saxony in a given context.
-
D.
strengthSweden
Indicates the level or degree of strength associated with Sweden in a given context.
-
E.
strengthDenmark
Indicates a measure or characterization of Denmark’s power, influence, or robustness in a given context.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02da9460819093a3ec5a3c62ea81 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.