Triple
T26359555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitwa pod Kockiem |
E660161
|
entity |
| Predicate | polishPOWsApprox |
P160451
|
FINISHED |
| Object | ok. 15000 jeńców polskich |
—
|
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: ok. 15000 jeńców polskich | Statement: [Bitwa pod Kockiem, polishPOWsApprox, ok. 15000 jeńców polskich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polishPOWsApprox Context triple: [Bitwa pod Kockiem, polishPOWsApprox, ok. 15000 jeńców polskich]
-
A.
polishUnit
Indicates that one entity performs the action of polishing or refining another entity, typically improving its surface, appearance, or quality.
-
B.
PolishObjective
Indicates that an entity is the target or goal of a polishing action or process.
-
C.
PolishUnit
Indicates that a unit is associated with Poland, typically by nationality, origin, or affiliation.
-
D.
objectivePoland
Indicates that something has Poland as its goal, target, or intended destination.
-
E.
пол
Indicates a relationship specifying an entity’s sex or gender classification.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ff21bc08190994f406feb484aad |
completed | May 2, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 10:50 p.m.