Triple
T20631728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artyomovsk |
E506971
|
entity |
| Predicate | wasAdministrativeStatus |
P38445
|
FINISHED |
| Object | city of oblast significance |
—
|
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: city of oblast significance | Statement: [Artyomovsk, wasAdministrativeStatus, city of oblast significance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAdministrativeStatus Context triple: [Artyomovsk, wasAdministrativeStatus, city of oblast significance]
-
A.
formerAdministrativeStatus
Indicates that an entity previously held, but no longer holds, a particular administrative status or role.
-
B.
administrativeStatusOfEntityRepresented
Indicates the current administrative or operational status assigned to the entity that is being represented.
-
C.
administrativeStatusCurrent
chosen
Indicates the current administrative status or condition of an entity within a governing or managing system.
-
D.
hasAdministrativeStatusSince
Indicates that an entity has held a particular administrative status continuously from a specified point in time onward.
-
E.
legalStatusAtApproval
Indicates the legal status or classification an entity held at the time it was formally approved.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0b0508819093c62a4ceaf860ce |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 16, 2026, 11:42 a.m.