Triple
T19388596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurgan Oblast |
E484998
|
entity |
| Predicate | establishedAsOblast |
P136260
|
FINISHED |
| Object | 20 February 1943 |
—
|
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: 20 February 1943 | Statement: [Kurgan Oblast, establishedAsOblast, 20 February 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsOblast Context triple: [Kurgan Oblast, establishedAsOblast, 20 February 1943]
-
A.
modernBelarusianAdministrativeRegion
Indicates that an entity is an administrative region within the contemporary state structure of Belarus.
-
B.
administrativeOkrug
Indicates that one entity functions as an administrative district or okrug governing or encompassing another entity within an administrative hierarchy.
-
C.
formerRegionBefore2016
Indicates that an entity was recognized as a region prior to the year 2016 but no longer holds that regional status after 2016.
-
D.
ustrójAdministracyjny
Indicates the type or structure of administrative system or governance under which an entity is organized or operates.
-
E.
formerAdministrativeTerritory
Indicates that one entity was previously an official administrative territory of another entity but no longer holds that 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b425e848190ab5ae8ae0a034fe2 |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e50213571881909cd7543a43b51986 |
completed | April 19, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.