Triple
T32894037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katerynopil |
E841416
|
entity |
| Predicate | raionReformDate |
P175556
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Katerynopil, raionReformDate, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raionReformDate Context triple: [Katerynopil, raionReformDate, 2020]
-
A.
partOfAdministrativeDivisionReform
Indicates that an entity is involved in, or results from, a reorganization or restructuring of administrative divisions.
-
B.
establishedAsOblast
Indicates that an administrative region was formally created or designated with the status of an oblast.
-
C.
regionBeforeReform
Indicates that a region is defined or considered as it existed prior to a specific reform or reorganization.
-
D.
lastReform
Indicates the most recent reform or change that was applied to an entity, typically linking the entity to its latest reform event or version.
-
E.
municipalityReform
Indicates a formal reorganization or restructuring of a municipality’s administrative boundaries, governance, or status.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d16b79dc8190ab0d4657f2ef9a5b |
completed | May 3, 2026, 4:39 a.m. |
Created at: May 1, 2026, 1:18 a.m.