Triple
T26359541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitwa pod Kockiem |
E660161
|
entity |
| Predicate | unitPoland |
P76617
|
FINISHED |
| Object | Samodzielna Grupa Operacyjna „Polesie” |
—
|
NE NERFINISHED |
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: Samodzielna Grupa Operacyjna „Polesie” | Statement: [Bitwa pod Kockiem, unitPoland, Samodzielna Grupa Operacyjna „Polesie”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitPoland Context triple: [Bitwa pod Kockiem, unitPoland, Samodzielna Grupa Operacyjna „Polesie”]
-
A.
PolishUnit
chosen
Indicates that a unit is associated with Poland, typically by nationality, origin, or affiliation.
-
B.
objectivePoland
Indicates that something has Poland as its goal, target, or intended destination.
-
C.
polishUnit
Indicates that one entity performs the action of polishing or refining another entity, typically improving its surface, appearance, or quality.
-
D.
lengthInPoland
Indicates that the specified length measurement is taken within the context or territory of Poland.
-
E.
ustrójPolityczny
Indicates a relationship where a political system or form of government is associated with or characterizes a given entity.
- 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_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. |
Created at: April 26, 2026, 10:50 p.m.