Triple
T14931251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharkov Governorate |
E372268
|
entity |
| Predicate | laterAdminSystemReplacedBy |
P92696
|
FINISHED |
| Object | okruhas of the Ukrainian SSR |
—
|
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: okruhas of the Ukrainian SSR | Statement: [Kharkov Governorate, laterAdminSystemReplacedBy, okruhas of the Ukrainian SSR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAdminSystemReplacedBy Context triple: [Kharkov Governorate, laterAdminSystemReplacedBy, okruhas of the Ukrainian SSR]
-
A.
formerAdministeredBy
Indicates that an entity was previously administered or managed by another entity, but is no longer under that administration.
-
B.
laterGoverningSystem
chosen
Indicates that one governing system succeeds and replaces another at a later point in time.
-
C.
replacedSystemUsedUntil
Indicates that one system was used up until it was replaced by another system.
-
D.
laterAdministrativeSuccessor
Indicates that one administrative entity succeeds another in governing authority or jurisdiction at a later time.
-
E.
laterManagedBy
Indicates that an entity was, at a subsequent time, managed or overseen by another entity.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64550dc8190ba44120df00ba498 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:36 a.m.