Triple
T37427187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Happy Moscow |
E930022
|
entity |
| Predicate | questionedIdeology |
P188066
|
FINISHED |
| Object | Soviet utopian project |
—
|
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: Soviet utopian project | Statement: [Happy Moscow, questionedIdeology, Soviet utopian project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questionedIdeology Context triple: [Happy Moscow, questionedIdeology, Soviet utopian project]
-
A.
ideology
Indicates the belief system or set of political, social, or philosophical principles that an entity adheres to or promotes.
-
B.
opposingIdeology
Indicates that two entities hold conflicting or mutually incompatible belief systems, doctrines, or ideological positions.
-
C.
ideologicalTheme
Indicates that one entity embodies, expresses, or is centrally concerned with a particular ideology or set of ideological beliefs.
-
D.
mainIdeologue
Indicates that one entity serves as the primary theorist or chief ideological architect behind another entity’s beliefs, policies, or movement.
-
E.
ideologyTargeted
Indicates that an entity is specifically targeted, opposed, or acted against because of its ideology or belief system.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.