Triple
T15248500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | So It Was |
E364449
|
entity |
| Predicate | hasPerspective |
P380
|
FINISHED |
| Object | Soviet |
E324881
|
NE 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: Soviet | Statement: [So It Was, hasPerspective, Soviet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Soviet Context triple: [So It Was, hasPerspective, Soviet]
-
A.
Soviets
chosen
Soviets were grassroots councils of workers, soldiers, and peasants that emerged as powerful political organs during the Russian Revolution and became a foundational element of the Soviet state.
-
B.
Sovetsk
Sovetsk is a town in Russia’s Kaliningrad Oblast, historically known as Tilsit and noted as the site where the 1807 Treaties of Tilsit were signed.
-
C.
MO USSR
MO USSR was the central government body responsible for directing and coordinating the armed forces of the Soviet Union.
-
D.
Marshal Sovetskogo Soyuza
Marshal Sovetskogo Soyuza was the highest military rank in the Soviet Union, equivalent to a five-star marshal and typically held by top commanders and defense ministers.
-
E.
Profsoyuznaya
Profsoyuznaya is a Moscow Metro station serving the Kaluzhsko–Rizhskaya Line in the south of the city.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f62b9c8190b9ad40e2d1912b63 |
completed | April 15, 2026, 9:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fedd4ac4e48190b011b34cb5205b68 |
completed | May 9, 2026, 7:07 a.m. |
Created at: April 10, 2026, 3:13 a.m.