Triple
T33711938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kłuszyn |
E863764
|
entity |
| Predicate | strengthPolishLithuanianCavalry |
P177648
|
FINISHED |
| Object | about 5,500 hussars |
—
|
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 5,500 hussars | Statement: [Battle of Kłuszyn, strengthPolishLithuanianCavalry, about 5,500 hussars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthPolishLithuanianCavalry Context triple: [Battle of Kłuszyn, strengthPolishLithuanianCavalry, about 5,500 hussars]
-
A.
PolishUnit
Indicates that a unit is associated with Poland, typically by nationality, origin, or affiliation.
-
B.
strengthPolishLithuanian
Indicates a comparative relationship where the strength or power of a Polish entity is evaluated relative to that of a Lithuanian entity.
-
C.
PolishCommander
Indicates that an entity serves as a military commander associated with Poland.
-
D.
polishForcesRole
Indicates that an entity serves in, is associated with, or has a specific role within the Polish armed forces.
-
E.
strengthBritishCavalry
Indicates the numerical or qualitative level of military power or effectiveness possessed by British cavalry forces.
- 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_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:43 a.m.