Triple
T21270029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Wizna |
E524229
|
entity |
| Predicate | strengthOfAttackers |
P47565
|
FINISHED |
| Object | over 40,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: over 40,000 soldiers | Statement: [Battle of Wizna, strengthOfAttackers, over 40,000 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthOfAttackers Context triple: [Battle of Wizna, strengthOfAttackers, over 40,000 soldiers]
-
A.
attackerStrength
chosen
Indicates the level or magnitude of power, force, or capability possessed by the attacking entity in a given interaction or scenario.
-
B.
numberOfAttacks
Indicates the count of distinct attack events associated with a given entity or interaction.
-
C.
offensiveStrength
Indicates the degree or capacity of an entity to carry out effective attacks or aggressive actions against an opponent.
-
D.
totalStrength
Indicates the overall magnitude or combined level of strength associated with an entity or group of entities.
-
E.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
- 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73651c9208190a87d45acd6fafaaa |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4:01 p.m.