Triple
T28868124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemirov |
E729057
|
entity |
| Predicate | timeInPolishLithuanianCommonwealth |
P138592
|
FINISHED |
| Object | before partitions of Poland |
—
|
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: before partitions of Poland | Statement: [Nemirov, timeInPolishLithuanianCommonwealth, before partitions of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInPolishLithuanianCommonwealth Context triple: [Nemirov, timeInPolishLithuanianCommonwealth, before partitions of Poland]
-
A.
countryDuringPolishLithuanianCommonwealth
chosen
Indicates that a country existed within or was part of the Polish–Lithuanian Commonwealth during a specified time period.
-
B.
timeZoneOnPolishSide
Indicates that the referenced time zone applies to the Polish side of a border or region.
-
C.
timeInPolandStart
Indicates the starting time at which something begins or becomes effective in Poland.
-
D.
timePeriodAsPartOfPolandStart
Indicates the starting point in time when an entity or region began to be part of Poland.
-
E.
timePeriodAsPartOfPolandEnd
Indicates the point in time when a given time period during which an entity was part of Poland comes to an end.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 6:49 a.m.