Triple
T29983591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSR Georgia |
E761662
|
entity |
| Predicate | leftTranscaucasianSFSR |
P60152
|
FINISHED |
| Object | 1936 |
—
|
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: 1936 | Statement: [SSR Georgia, leftTranscaucasianSFSR, 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leftTranscaucasianSFSR Context triple: [SSR Georgia, leftTranscaucasianSFSR, 1936]
-
A.
formerSovietRepublic
Indicates that an entity is a country or region that was once part of the Soviet Union but is now independent.
-
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.
startDateAsPartOfTranscaucasianSFSR
Indicates the date on which something began while it was part of the Transcaucasian Soviet Federative Socialist Republic.
-
D.
usedInTranscaucasia
Indicates that something is utilized or applied within the geographic region of Transcaucasia.
-
E.
endDateAsPartOfTranscaucasianSFSR
chosen
Indicates the date on which something (such as a status, membership, or existence) ended while it was part of the Transcaucasian Soviet Federative Socialist Republic.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678db0a488190a4b8f79cb1949749 |
completed | May 2, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:35 p.m.