Triple
T30124382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maidan Konstytutsii |
E765648
|
entity |
| Predicate | hasFormerSovietName |
P191012
|
FINISHED |
| Object | Radyanska |
—
|
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: Radyanska | Statement: [Maidan Konstytutsii, hasFormerSovietName, Radyanska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerSovietName Context triple: [Maidan Konstytutsii, hasFormerSovietName, Radyanska]
-
A.
homeCountryDuringSovietEra
Indicates the country that was considered an entity’s home country during the period of the Soviet Union’s existence.
-
B.
partOfFormerSovietRepublic
Indicates that one entity was a territorial or administrative component of a country that was formerly a republic of the Soviet Union.
-
C.
formerSovietRepublic
Indicates that an entity is a country or region that was once part of the Soviet Union but is now independent.
-
D.
isSovietCounterpartOf
Indicates that one entity serves as the Soviet-era equivalent or counterpart to another entity in role, function, or status.
-
E.
returnedFromSovietUnion
Indicates that an entity came back from the Soviet Union to another place after having been there.
- F. None of above. chosen
Provenance (4 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: April 29, 2026, 7:14 p.m.