Triple
T17659259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сквира |
E440206
|
entity |
| Predicate | isRaionCenterOf |
P86708
|
FINISHED |
| Object | Сквирський район |
—
|
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: Сквирський район | Statement: [Сквира, isRaionCenterOf, Сквирський район]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRaionCenterOf Context triple: [Сквира, isRaionCenterOf, Сквирський район]
-
A.
isAdministrativeCenterIn
chosen
Indicates that an entity serves as the main administrative or governmental center located within a specified larger area or jurisdiction.
-
B.
isTransportCenterOf
Indicates that a location functions as a primary hub or central node for transportation activities serving another area or network.
-
C.
servesAsRegionalCenterFor
Indicates that one entity functions as the primary administrative, economic, or service hub for a surrounding region or group of entities.
-
D.
administrativeCentreType
Indicates the specific kind or level of administrative center that a place serves as within an administrative hierarchy.
-
E.
isNationalAdministrativeCenter
Indicates that a location serves as the primary administrative or governmental center for a nation.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea469448190b2753571f8493aef |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:39 a.m.