Triple
T10531394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonian SSR |
E248447
|
entity |
| Predicate | incorporationDateIntoUSSR |
P9024
|
FINISHED |
| Object | 6 August 1940 |
—
|
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: 6 August 1940 | Statement: [Estonian SSR, incorporationDateIntoUSSR, 6 August 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporationDateIntoUSSR Context triple: [Estonian SSR, incorporationDateIntoUSSR, 6 August 1940]
-
A.
joinedSovietUnionAfter
Indicates that one entity became a member of or was incorporated into the Soviet Union after another specified time or event.
-
B.
joinedRussianEmpire
Indicates that an entity became part of, or was incorporated into, the Russian Empire.
-
C.
statusInSovietUnion
Indicates the legal, social, or political standing an entity held within the Soviet Union.
-
D.
annexationDate
chosen
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
-
E.
establishedAsSocialistState
Indicates that an entity formally created or declared another entity to be a socialist state as its system of governance.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a16915c8190ac4f3fd5e43c5fed |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:30 p.m.