Triple
T33711939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kłuszyn |
E863764
|
entity |
| Predicate | strengthRussianSwedish |
P177826
|
FINISHED |
| Object | approximately 30,000–40,000 troops |
—
|
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–40,000 troops | Statement: [Battle of Kłuszyn, strengthRussianSwedish, approximately 30,000–40,000 troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthRussianSwedish Context triple: [Battle of Kłuszyn, strengthRussianSwedish, approximately 30,000–40,000 troops]
-
A.
strengthSweden
Indicates the level or degree of strength associated with Sweden in a given context.
-
B.
strengthRussia
Indicates a relationship where a level, measure, or display of strength is attributed to or associated with Russia.
-
C.
strengthPolishLithuanian
Indicates a comparative relationship where the strength or power of a Polish entity is evaluated relative to that of a Lithuanian entity.
-
D.
strengthDenmark
Indicates a measure or characterization of Denmark’s power, influence, or robustness in a given context.
-
E.
strengthBulgaria
Indicates a relationship where something possesses or demonstrates strength specifically associated with Bulgaria.
- 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f70519f114819080659840c04d7911 |
completed | May 3, 2026, 8:19 a.m. |
Created at: May 1, 2026, 1:43 a.m.