Triple
T33780322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teofipol |
E865635
|
entity |
| Predicate | raionAfter2020 |
P117243
|
FINISHED |
| Object | Khmelnytskyi Raion |
—
|
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: Khmelnytskyi Raion | Statement: [Teofipol, raionAfter2020, Khmelnytskyi Raion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raionAfter2020 Context triple: [Teofipol, raionAfter2020, Khmelnytskyi Raion]
-
A.
raionReformDate
Indicates the date on which an administrative district (raion) underwent a formal reform or reorganization.
-
B.
establishedAsOblast
Indicates that an administrative region was formally created or designated with the status of an oblast.
-
C.
modernBelarusianAdministrativeRegion
Indicates that an entity is an administrative region within the contemporary state structure of Belarus.
-
D.
partOfAdministrativeDivisionReform
chosen
Indicates that an entity is involved in, or results from, a reorganization or restructuring of administrative divisions.
-
E.
formerRegionBefore2016
Indicates that an entity was recognized as a region prior to the year 2016 but no longer holds that regional status after 2016.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.