Triple
T25019438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitwa o Kołobrzeg |
E626531
|
entity |
| Predicate | zakończyłaSię |
P18462
|
FINISHED |
| Object | 1945-03-18 |
—
|
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: 1945-03-18 | Statement: [Bitwa o Kołobrzeg, zakończyłaSię, 1945-03-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zakończyłaSię Context triple: [Bitwa o Kołobrzeg, zakończyłaSię, 1945-03-18]
-
A.
alsoEnded
Indicates that one event or state concluded in addition to another already mentioned event or state.
-
B.
concluded
Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
-
C.
concludedWith
Indicates that an event, process, or interaction ended or was finalized by a specific outcome, action, or state.
-
D.
wasConcludedUnder
Indicates that an agreement, decision, or process was finalized according to, or within the framework of, a specific set of conditions, rules, authority, or context.
-
E.
concludedDuring
chosen
Indicates that an event, process, or state ended within the temporal bounds of another specified time period or event.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44ba9108c8190aca5c07f277d82b8 |
completed | May 1, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:06 a.m.