Triple
T38378624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrgyzstan Time |
E893694
|
entity |
| Predicate | usedInSovietEraRegion |
P130568
|
FINISHED |
| Object | Kirghiz SSR |
—
|
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: Kirghiz SSR | Statement: [Kyrgyzstan Time, usedInSovietEraRegion, Kirghiz SSR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInSovietEraRegion Context triple: [Kyrgyzstan Time, usedInSovietEraRegion, Kirghiz SSR]
-
A.
usedInFormerEasternBlocCountry
Indicates that something was used within a country that was part of the former Eastern Bloc.
-
B.
homeCountryDuringSovietEra
Indicates the country that was considered an entity’s home country during the period of the Soviet Union’s existence.
-
C.
locatedInRegionOfRussia
Indicates that one entity is geographically situated within a specified region of Russia.
-
D.
timePeriodAsPartOfSovietUnion
Indicates that a specified time period falls within the historical span during which an entity was part of the Soviet Union.
-
E.
timePeriodOfSovietUse
chosen
Indicates the span of time during which something was used or operated under Soviet control or by Soviet authorities.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 3, 2026, 4:31 p.m.