Triple
T628915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kunersdorf |
E15881
|
entity |
| Predicate | strengthPrussia |
P11878
|
FINISHED |
| Object | approximately 50,000–60,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 50,000–60,000 soldiers | Statement: [Battle of Kunersdorf, strengthPrussia, approximately 50,000–60,000 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthPrussia Context triple: [Battle of Kunersdorf, strengthPrussia, approximately 50,000–60,000 soldiers]
-
A.
warTimeStrengthApprox
chosen
Indicates an approximate measure of an entity’s military strength or capacity during a time of war.
-
B.
countryOfDefeatedSide
Indicates the country to which the losing or defeated side in a conflict, competition, or confrontation belongs.
-
C.
warPower
Indicates the authority, capability, or legal power to initiate, conduct, or manage acts of war or armed conflict.
-
D.
rankInPentarchy
Indicates the relative hierarchical position an entity holds within the structure of the pentarchy.
-
E.
strength
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e5b5a308190a62165f9275e2f5f |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49d01b29081908be87e4cd7726ff1 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.