Triple
T19425327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet mass organizations system |
E485964
|
entity |
| Predicate | actualPractice |
P135830
|
FINISHED |
| Object | social pressure to join |
—
|
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: social pressure to join | Statement: [Soviet mass organizations system, actualPractice, social pressure to join]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualPractice Context triple: [Soviet mass organizations system, actualPractice, social pressure to join]
-
A.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
B.
practice
Indicates that an entity regularly performs an activity or skill, typically to improve proficiency or maintain competence.
-
C.
hadPractice
Indicates that an entity engaged in or participated in a practice session or rehearsal.
-
D.
usedInPractice
Indicates that something is actually applied or implemented in real-world practice rather than just being theoretical or proposed.
-
E.
approvedPractice
Indicates that a particular practice, method, or procedure has been formally reviewed and granted official approval for use or adoption.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63218772c8190a48b6cb01bd12b73 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.