Triple
T37881833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertsa region |
E944886
|
entity |
| Predicate | postSovietCountry |
P127489
|
FINISHED |
| Object | Ukraine |
—
|
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: Ukraine | Statement: [Hertsa region, postSovietCountry, Ukraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postSovietCountry Context triple: [Hertsa region, postSovietCountry, Ukraine]
-
A.
postSovietStatus
Indicates that an entity has a political, social, or historical status related to the period or conditions following the dissolution of the Soviet Union.
-
B.
formerSovietRepublic
chosen
Indicates that an entity is a country or region that was once part of the Soviet Union but is now independent.
-
C.
partOfFormerSovietRepublic
Indicates that one entity was a territorial or administrative component of a country that was formerly a republic of the Soviet Union.
-
D.
countryBefore1991
Indicates that the specified country existed or held the relevant status prior to the year 1991.
-
E.
countryAfter1991
Indicates that the entity is recognized as a country that came into existence or gained its current sovereign status after the year 1991.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.