Triple
T32948852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monastyryshche |
E842884
|
entity |
| Predicate | raion |
P89705
|
FINISHED |
| Object | Uman 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: Uman Raion | Statement: [Monastyryshche, raion, Uman Raion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raion Context triple: [Monastyryshche, raion, Uman Raion]
-
A.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
B.
raionReformDate
Indicates the date on which an administrative district (raion) underwent a formal reform or reorganization.
-
C.
establishedAsOblast
Indicates that an administrative region was formally created or designated with the status of an oblast.
-
D.
administrativeOkrug
chosen
Indicates that one entity functions as an administrative district or okrug governing or encompassing another entity within an administrative hierarchy.
-
E.
ustrójAdministracyjny
Indicates the type or structure of administrative system or governance under which an entity is organized or operates.
- 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:21 a.m.