Triple
T31519924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leninabad |
E804179
|
entity |
| Predicate | topLevelAdministrativeUnitDuringUSSR |
P172263
|
FINISHED |
| Object | Tajik 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: Tajik SSR | Statement: [Leninabad, topLevelAdministrativeUnitDuringUSSR, Tajik SSR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLevelAdministrativeUnitDuringUSSR Context triple: [Leninabad, topLevelAdministrativeUnitDuringUSSR, Tajik SSR]
-
A.
ownerDuringUSSR
Indicates that one entity was the owner of another entity specifically during the period of the USSR’s existence.
-
B.
UNMembershipThroughUSSR
Indicates that an entity’s membership in the United Nations is obtained or held by virtue of, or through succession to, the membership previously held by the USSR.
-
C.
homeCountryDuringSovietEra
Indicates the country that was considered an entity’s home country during the period of the Soviet Union’s existence.
-
D.
formerSovietRepublic
Indicates that an entity is a country or region that was once part of the Soviet Union but is now independent.
-
E.
statusInSovietUnion
Indicates the legal, social, or political standing an entity held within the Soviet Union.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 30, 2026, 9:55 p.m.